Hi,
We've developped an application where a webapp agent communicates using Invoke/rmi with a server servlet serviced by our handler (MySubSys.class):
----------------------- ------------------------------------- | webapp agent .invoke | ---RMI---> | servlet -> handler (MySubSys.class) | ----------------------- -------------------------------------
<server>
<mbean code="org.jboss.remoting.transport.Connector"
name="jboss.remoting:service=Connector,transport=RMI"
display-name="MySubSys Socket transport Connector">
<attribute name="Configuration">
<config>
<invoker transport="rmi">
<attribute name="registryPort" isParam="true">8053</attribute>
<attribute name="serverBindAddress">${jboss.bind.address}</attribute>
<attribute name="serverBindPort">8052</attribute>
</invoker>
<handlers>
<handler subsystem="MYSUBSYS">com.subsys.MySubSys</handler>
</handlers>
</config>
</attribute>
<depends>jboss.jca:service=DataSourceBinding,name=subsysDS</depends>
</mbean>
</server>
Not sure if pooled invokers will help you, as they keep connections open for longer. If the problem is a large number of clients why not going over http?