[jboss-jira] [JBoss JIRA] Updated: (JBREM-731) Address of secondary server socket should be acquired each time a control connection is created.
[ http://jira.jboss.com/jira/browse/JBREM-731?page=all ]
Ron Sigal updated JBREM-731:
----------------------------
Fix Version/s: 2.2.2.GA
Adding fix version 2.2.2.GA, since this issue was, in fact, resolved in 2.2.2.GA.
Address of secondary server socket should be acquired each time a
control connection is created.
------------------------------------------------------------------------------------------------
Key: JBREM-731
URL: http://jira.jboss.com/jira/browse/JBREM-731
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.2.0.GA (Bluto)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.GA
Scenario: Client is connected to a server, server dies, and server is restarted (with
same InvokerLocator). The new server creates a secondary server socket on a different
port than the previous server, but the client invoker retains the old secondary server
socket InvokerLocator. When a new Client is created, the old client invoker gets reused,
and it isn't possible to create a control connection.
--
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