[ http://jira.jboss.com/jira/browse/JBREM-534?page=comments#action_12339906 ] Ron Sigal commented on JBREM-534: --------------------------------- This is indeed a Multiplex issue. The client invoker is closely tied to the server invoker because it depends on a persistent socket connection to the server. This situation is remedied by some changes to InputMultiplexor, OutputMultiplexor, MultiplexingManager, MultiplexClientInvoker, and MultiplexServerInvoker. Whenever InputMultiplexor or OutputMultiplexor detect a broken connection, they inform MultiplexingManager, which informs all of the virtual sockets in its group. When MultiplexClientInvoker.createSocket() finds that its priming socket has been contacted about a broken connection, it attempts to create a new priming socket connected to a new server at the same address as the one that went down. The complication is that there might be a virtual callback MultiplexServerInvoker in the same group, bound to a particular bind port. Attempting to create a new socket bound to the same port can cause a bind exception, so MultiplexClientInvoker gets an arbitrary bind port and restarts the MultiplexServerInvoker with a new VirtualServerrSocket bound to the new bind port. If the Connector was created explicitly by the user, the user will have to query the Connector for its new InvokerLocator before re-registering any callback handlers. -- 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