[jboss-jira] [JBoss JIRA] Commented: (JBREM-784) Use separate maps for control sockets and ordinary sockets in BisocketClientInvoker

[Ron Sigal (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBREM-784?page=comments#action_12371142 ] 
            
Ron Sigal commented on JBREM-784:
---------------------------------

It's possible that the confusion was due to another issue, JBREM-785.  However, there is still the possibility that the confusion could arise during a switch to a new control connection.

The fix has been applied to branch remoting_2_2_0_GA.

Unit test: org.jboss.test.remoting.transport.bisocket.SeparateControlSocketsTestCase.

> Use separate maps for control sockets and ordinary sockets in BisocketClientInvoker
> -----------------------------------------------------------------------------------
>
>                 Key: JBREM-784
>                 URL: http://jira.jboss.com/jira/browse/JBREM-784
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 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
>
>
> A race condition can cause control sockets and ordinary sockets to be confused with each other.  In particular, in some runs of the JBossMessaging test org.jboss.test.messaging.jms.stress.SeveralClientsStressTest, it was observed that a connection that the client side took to be a control connection was used as an ordinary connection by the server side.  The result was that org.jboss.remoting.transport.bisocket.BisocketServerInvoker.ControlConnectionThread.run() received unrecognized command.

-- 
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