[jboss-remoting-issues] [JBoss JIRA] Created: (JBREM-1147) BisocketClientInvoker.createSocket() in callback mode should check for replaced control socket

[Ron Sigal (JIRA)]

BisocketClientInvoker.createSocket() in callback mode should check for replaced control socket
----------------------------------------------------------------------------------------------

                 Key: JBREM-1147
                 URL: https://jira.jboss.org/jira/browse/JBREM-1147
             Project: JBoss Remoting
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 2.2.3, 2.5.1 (Flounder)
            Reporter: Ron Sigal
            Assignee: Ron Sigal
             Fix For: 2.5.2 (Flounder), 2.2.3.SP1


When running as a callback client invoker, org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket() creates a socket by writing a request on the control socket and waiting for the client side to connect to the secondary ServerSocket.  If the control socket fails and is replaced, however, it may not be possible to write the request, or the written request might get lost.  Therefore, createSocket() should periodically check if the control socket has been replaced, and, if it has been, the request to create a socket should be rewritten.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira