[jboss-jira] [JBoss JIRA] Commented: (JBREM-787) Move network i/o in BisocketClientInvoker constructor to handleConnect()
[ http://jira.jboss.com/jira/browse/JBREM-787?page=comments#action_12371140 ]
Ron Sigal commented on JBREM-787:
---------------------------------
The fix has been applied to branch remoting_2_2_0_GA.
There is no specific unit test.
Move network i/o in BisocketClientInvoker constructor to
handleConnect()
------------------------------------------------------------------------
Key: JBREM-787
URL: http://jira.jboss.com/jira/browse/JBREM-787
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.0.SP4, 2.2.1.GA
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto), 2.2.0.SP4_CP02, 2.2.1.SP1
The org.jboss.remoting.transport.bisocket.BisocketClientInvoker constructor is called by
org.jboss.remoting.InvokerRegistry.createClientInvoker inside a synchronization block.
InvokerRegistry.destroyClientInvoker uses the same lock, so a network problem in the
BisocketClientInvoker could affect other threads.
--
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