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

[Andre Parodi (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBREM-1005?page=comments#action_12419968 ] 
            
Andre Parodi commented on JBREM-1005:
-------------------------------------

I am having trouble with my heap filling up with these ControlMonitorTimerTasks. I have set my pingFrequency to 300 000 ( 5 min). Is there any reason that the default is set so unreasonably high? Should I be worried about adverse effects of having the pingFrequency set to 5 mins?

This would be a tactical fix until SP9 is available.

> 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
>
>
> 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: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira