[jboss-jira] [JBoss JIRA] Commented: (JBREM-729) Make multiplex server invoker more robust
[ http://jira.jboss.com/jira/browse/JBREM-729?page=comments#action_12357415 ]
Ron Sigal commented on JBREM-729:
---------------------------------
Made various small changes to multiplex transport. Most importantly, (1)
MultiplexServerInvoker.run() will not stop in case of EOFException, and (2)
MultiplexServerInvoker sets timeout on MasterServerInvoker, so that it doesn't get
hung up in protocol processing.
Waiting for cruisecontrol test results.
Make multiplex server invoker more robust
-----------------------------------------
Key: JBREM-729
URL: http://jira.jboss.com/jira/browse/JBREM-729
Project: JBoss Remoting
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto)
Claudia Richter has reported some problems using Remoting JNDI detection with multiplex
transport. If the JNDI heartbeat is looking for an old socket invoker at an address and
port where a multiplex invoker currently runs, the multiplex invoker can get hung up
trying to process in invocation intended for the socket invoker. It should be able to
tolerate unexpected inputs. In particular, MultiplexServerInvoker should set a timeout on
the MasterServerSocket so that it doesn't get hung up in accept().
--
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