[jboss-jira] [JBoss JIRA] Commented: (JBREM-748) BisocketClientInvoker should guard agains scheduling on an expired Timer

Ron Sigal (JIRA) jira-events at lists.jboss.org
Sat Jun 2 01:46:08 EDT 2007


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

The solution is to catch any IllegalStateException thrown when attempting to schedule a PingTimerTaks on the static Timer and recreate the Timer.

Unit test:  org.jboss.test.remoting.transport.bisocket.TimerReuseTestCase.

> BisocketClientInvoker should guard agains scheduling on an expired Timer
> ------------------------------------------------------------------------
>
>                 Key: JBREM-748
>                 URL: http://jira.jboss.com/jira/browse/JBREM-748
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.Beta1 (Pinto)
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> In two places, org.jboss.remoting.transport.bisocket.BisocketClientInvoker schedules a PingTimerTask on the Timer referenced by the static variable timer.  The problem is that if the Timer has been around for a while and all of its tasks have completed, it could have entered a state in which in can no longer schedule new tasks.

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