[jboss-jira] [JBoss JIRA] Commented: (JBREM-851) In LeasePinger and TimerUtil replace Timer if it has shut down

[Ron Sigal (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBREM-851?page=comments#action_12397604 ] 
            
Ron Sigal commented on JBREM-851:
---------------------------------

This issue is not relevant to LeasePinger, each of which gets its own Timer, where the TimerTask is never removed.

However, TimerUtil has been fixed so that it will recreate the Timer if necessary.

Testing:  testReplaceTimer() has been added to org.jboss.test.remoting.util.TimerUtilTestCase.

> In LeasePinger and TimerUtil replace Timer if it has shut down
> --------------------------------------------------------------
>
>                 Key: JBREM-851
>                 URL: http://jira.jboss.com/jira/browse/JBREM-851
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
>            Reporter: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> When all of the TimerTasks running in a java.util.TimerTask have shut down, the TImer will also shut down, at which point it will accept no more TimerTasks.  There are places in Remoting where there should be a test which will create a new Timer the attempt to schedule a TimerTask results in an exception.
> Two places the problem exists:
> 1. org.jboss.remoting.LeasePinger, and
> 2. org.jboss.remoting.util.TimerUtil.
> A similar problem is described in JBREM-748 "BisocketClientInvoker should guard agains scheduling on an expired Timer"
> Reported by James on Remoting forum.

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