[jboss-remoting-issues] [JBoss JIRA] Closed: (JBREM-1005) Prevent build up of cancelled TimerTasks in bisocket transport

[Ron Sigal (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBREM-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ron Sigal closed JBREM-1005.
----------------------------

    Resolution: Done


Tests are passing in hudson.

> Prevent build up of cancelled TimerTasks in bisocket transport
> --------------------------------------------------------------
>
>                 Key: JBREM-1005
>                 URL: https://jira.jboss.org/jira/browse/JBREM-1005
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.GA (Pinto), 2.2.2.SP8
>            Reporter: Ron Sigal
>            Assignee: Ron Sigal
>             Fix For: 2.4.0.SP1, 2.2.2.SP9
>
>         Attachments: jboss-remoting.jar
>
>
> The behavior of java.util.Timer and java.util.TimerThread is such that a cancelled java.util.TimerTask is removed from the Timer's queue the next time it is executed after being cancelled.  JBossMessaging has effectively disabled the bisocket control connection ping mechanism by setting the parameter "pingFrequency" to 214748364, which means that the org.jboss.remoting.transport.bisocket.BisocketServerInvoker.ControlMonitorTimerTask gets created but essentially "never" runs.  So when a JBM connection closes, it also shuts down the Remoting bisocket connection, which causes the ControlMonitorTimerTask to get cancelled, but it remains in the Timer queue "forever".

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira