Re: [jboss-user] [JBoss Remoting] - Remoting - "replacing control socket" Question

Ron Sigal [http://community.jboss.org/people/ron.sigal%40jboss.com] replied to the discussion "Remoting - "replacing control socket" Question" To view the discussion, visit: http://community.jboss.org/message/557158#557158 -------------------------------------------------------------- H Vidhya, Not necessarily.  currentPoolSize represents the number of threads currently either (1) actively executing an invocation, or (2) sitting in a read() waiting for the next invocation.  The latter threads will remain in that state until the read() times out, which, for JBossMessaging, is never, since remoting-bisocket-service.xml sets the "timeout" value to 0.  (Note, by the way, that the read() will be interrupted and the thread made available for reuse if the maximum number of threads is reached.)  Changing the control socket doesn't have any effect on this behavior.  If you're concerned about the number of threads, there is an "idleTimeout" parameter which, if set to a value greater than 0, will shut down threads that haven't been used for "idleTimeout" seconds.  Or, you could set "timeout" to a finite value. Well, it used to be that JBossMessaging always turned off the ping, but I believe (and I think they now believe) that doing so can lead to problems.  The trick is to find the right ping interval to avoid too many spurious timeouts due to busy servers or congested networks. -Ron -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/557158#557158] Start a new discussion in JBoss Remoting at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]