[
http://jira.jboss.com/jira/browse/JBREM-551?page=comments#action_12339820 ]
Ron Sigal commented on JBREM-551:
---------------------------------
Have made some changes to MultiplexServerInvoker, OutputMultiplexor, and Protocol so that
virtual socket groups shut down more gracefully. Not sure if this solves the test
failure, however.
org.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)
failure
------------------------------------------------------------------------------------------------
Key: JBREM-551
URL:
http://jira.jboss.com/jira/browse/JBREM-551
Project: JBoss Remoting
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 2.0.0.CR1 (Boon)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.0.0.CR1 (Boon)
There seem to be two sources of exceptions here:
1. When a Connector shuts down and a MultiplexingManager is still running on remote end
(not sure how this happened), the remote OutputMultiplexor will get "Broken
pipe" exceptions.
2. When a Connector shuts down, the master MultiplexServerInvoker can shut down a virtual
MultiplexServerInvoker, interruptting an acceptThread, which cause the VirtualServerSocket
to think it has reached end of file.
Not sure how these problems caused the test to fail, however.
--
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