[jboss-remoting-issues] [JBoss JIRA] Updated: (JBREM-577) Investigate failure of org.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase, jdk 1.4, on cruisecontrol

[Ron Sigal (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBREM-577?page=all ]

Ron Sigal updated JBREM-577:
----------------------------

    Fix Version/s:     (was:  2.4.0.Beta2 (Pinto))

Removed fix version.

> Investigate failure of org.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase, jdk 1.4, on cruisecontrol
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBREM-577
>                 URL: http://jira.jboss.com/jira/browse/JBREM-577
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA (Boon)
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>
> This test is failing rather consistently in testRule4ServerFirst() on cruisecontrol, even though this particular failure can't be reproduced on any other environment.   In case the problem is more than environmental, i.e., a real problem in Multiplex, some additional log statements will be added to MultiplexServerInvoker and OutputMultiplexor.  
> What is happening is that in runPushCallbackTests(), the message "stopped callback Connector" appears, but then the test dies before the callback Connector completes its shut down.  It would be nice to believe that there is a deadlock, but none is evident, unless it's due to a problem with Collections.synchronizedMap in jdk 1.4.  Note that this problem never occurs in the jdk 1.5 cruisecontrol tests.

-- 
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