Hi, here the situation : - A client make remoting call on a object using rmi via org.jboss.remoting.Client and org.jboss.remoting.InvokerLocator. - On the server side, we use ServerInvocationHandler and implement the method invoke(...). Using jetty, we add on jboss-service.xml this configuration : | <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> | This part is ok. But a large number of Clients have to connected on the server. When we made some tests, we note that when too much clients are connected, the others clients which want to connect them self to the server see their connections refused due to open connection limitation. I wonder to know if there is a way to increase the number of socketConnection, socketTimeout, ... for RMI in order to add it on the jboss-service.xml. Thanks ;) Bye. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055120#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...