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

Prevent build up of cancelled TimerTasks in bisocket transport -------------------------------------------------------------- Key: JBREM-1005 URL: http://jira.jboss.com/jira/browse/JBREM-1005 Project: JBoss Remoting Issue Type: Bug Security Level: Public(Everyone can see) Affects Versions: 2.2.2.SP8, 2.4.0.GA (Pinto) Reporter: Ron Sigal Assigned To: 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".