hello My JBoss version is 4.0.4GA. The JBoss Remoting version is 1.4.3 (I can see it in boss-remoting.jar : meta-inf/manifest.mf).For testing my configuration, I create 500 threads in my client. Each thread invoke an EJB method that simulate an execution with Thread.sleep(time). My configuration is the follow : | <invoker transport="socket"> | <attribute name="serverBindAddress">${jboss.bind.address}</attribute> | <attribute name="serverBindPort">3873</attribute> | <attribute name="maxPoolSize">400</attribute> | <attribute name="backlog">200</attribute> | <attribute name="clientMaxPoolSize" isParam="true">50</attribute> | <attribute name="timeout" isParam="true">60000</attribute> | <attribute name="numberOfRetries" isParam="true">60</attribute> | </invoker> | | I have volontary set the maxpoolSize to 400 for testing the server side behavior of waiting queue (parameterized with 'backlog' value). When the sleep time is greater than 3000 ms, one or more client threads throws an exception : | java.lang.reflect.UndeclaredThrowableException:null | | caused by : java.rmi.MarshalException:Socket timed out. Waited 60000 milliseconds for response while calling on InvokerLocator [socket://10.20.1.113:3873/?clientMaxPoolSize=50&numberOfRetries=60&timeout=60000]; nested exception is: java.net.SocketTimeoutException: Read timed out | | caused by : java.net.SocketTimeoutException:Read timed out | When all client threads have finished, I see that on the JMX Console the value of currentClientPoolSize > 0. Its value is exactly the same that number of client threads that failed with SocketTimeoutException. I conclued that the first 400 server threads work fine (corresponding to the maxPoolSize). Then, some of the next 100 server threads never return in an "available" state. Is it a bug on the 1.4.3 version or a configuration problem ? Thanks for your help. Nicolas Medoc. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4120475#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...