[jboss-jira] [JBoss JIRA] Commented: (JBREM-596) Lease stops working if the First Client using the same Locator is closed

Tom Elrod (JIRA) jira-events at jboss.com
Wed Sep 20 00:41:53 EDT 2006


    [ http://jira.jboss.com/jira/browse/JBREM-596?page=comments#action_12343639 ] 
            
Tom  Elrod commented on JBREM-596:
----------------------------------

Have updated code so that client invoker is responsible for handling lease management for all Clients using that client invoker.  The org.jboss.test.remoting.lease.socket.multiple package test case is passing now.

The main benefit for this (other than fixing original bug) is that instead of having a thread per Client doing lease ping, will only be one thread per client invoker (regardless of number of Clients using that client invoker).  

This change does raise some issues with regards to some of the more obscure behaviors, which have been listed in forum post - http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972805#3972805

> Lease stops working if the First Client using the same Locator is closed
> ------------------------------------------------------------------------
>
>                 Key: JBREM-596
>                 URL: http://jira.jboss.com/jira/browse/JBREM-596
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: callbacks
>    Affects Versions: 2.0.0.GA (Boon)
>            Reporter: Clebert Suconic
>         Assigned To: Tom  Elrod
>             Fix For: 2.2.0.Beta1 (Bluto)
>
>
> If you use always the same locator (say if you need socket pool working), and if you close the first Client opened, Lease will stop as Lease is associated with the Client and not with the Invoker (what is wrong IMO)
> Lease should be associated with AbstractInvoker, as the property for Lease will determine an unique ClientInvoker on InvokerRegistry.
> Test org.jboss.test.remoting.lease.socket.multiple has the scenario for this failure.

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

        



More information about the jboss-jira mailing list