That particular timeout value is specified by the "connectionWait" parameter, which defaults to 30000, so you could add, for example, | <attribute name="connectionWait" isParam="true">60000</attribute> | to remoting-bisocket-service.xml, JBM's configuration file. Note that for this timeout to occur, the MicroSocketClientInvoker must already have 50 (by default) connections already in use, before waiting 30 seconds for one of them to return to the connection pool. Does that sound plausible for your test? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4202302#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...