[jboss-dev-forums] [Design of JBoss Remoting, Unified Invokers] - Re: Remoting 2: Timeout waiting on socket for InvokerLocator

[ron.sigal@jboss.com]

"sentcs" wrote : 
  | how to increase the number of connections
  | 

Normally, the default value is 50, as I said, and, normally, the parameter to set is "clientMaxPoolSize".  However, setting that value in JBossMessaging's remoting-bisocket-service.xml would also affect callback clients on the server side, which the JBM guys didn't want to do, so they created a JBM specific parameter, "JBM_clientMaxPoolSize".  Also, I see that they set it to "200" in remoting-bisocket-service.xml.

"sentcs" wrote : 
  | And i want know, any impact if i am going to change the number of connection
  | 

If you are actually exhausting the pool, and you increase the pool size, then you could get more activity on the client, for better or worse.  Also, a single client could take up more of the server's resources.  If the server isn't overloaded, then you might consider increasing the number of worker threads on the server, using the "maxPoolSize" parameter.  The default is 300.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207202#4207202

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207202