[jboss-jira] [JBoss JIRA] Closed: (JBREM-600) org.jboss.test.remoting.lease.multiplex.MultiplexLeaseTestCase fails

[Ron Sigal (JIRA)]

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

Ron Sigal closed JBREM-600.
---------------------------

    Resolution: Done

Master and virtual MultiplexServerInvokers need to share the connectionNotifier table. 

> org.jboss.test.remoting.lease.multiplex.MultiplexLeaseTestCase fails
> --------------------------------------------------------------------
>
>                 Key: JBREM-600
>                 URL: http://jira.jboss.com/jira/browse/JBREM-600
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: transport-multiplex
>    Affects Versions: 2.0.0.GA (Boon)
>            Reporter: Tom  Elrod
>         Assigned To: Ron Sigal
>             Fix For:  2.2.0.Beta1 (Bluto)
>
>
> When run org.jboss.test.remoting.lease.multiplex.MultiplexLeaseTestCase, the test fails.  From debugging, the ServerInvoker's leaseManagement variable is not set to true when it's invoke() method is called (thus by-passing leasing).  
> Also noticed when debugging that when Connector.addConnectionListener() calls:
> invoker.addConnectionListener(listener);
> that the invoker instance was MultiplexServerInvoker[master] (this is where the leaseManagement variable gets set to true) and when the PING invocation request is processed within ServerInvoker.invoke() method (where checks to see if leaseManagement variable is true and is not), the invoker instance is MultiplexServerInvoker[virtual:/127.0.0.1:5400->/127.0.0.1:1914].

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