[
http://jira.jboss.com/jira/browse/JBREM-937?page=all ]
Ron Sigal closed JBREM-937.
---------------------------
Resolution: Done
Unit test: org.jboss.test.remoting.transport.bisocket.threadpool.ServerThreadReuseTestCase
passes.
From support case:
This fix looks good. I've retested in my dev env, and am confident that this will
fix the problem.
Callback BisocketServerInvoker should reuse available ServerThreads
-------------------------------------------------------------------
Key: JBREM-937
URL:
http://jira.jboss.com/jira/browse/JBREM-937
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.2.2.SP5
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.2.2.SP6
When
org.jboss.remoting.transport.bisocket.BisocketServerInvoker.ControlConnectionThread.run()
creates a new socket, it always creates a new
org.jboss.remoting.transport.socket.ServerThread. Instead, it should look in
org.jboss.remoting.transport.socket.SocketServerInvoker.threadpool for existing
ServerThreads waiting to be reused.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira