[jboss-jira] [JBoss JIRA] Updated: (JBREM-676) TimerTasks run by TimerUtil should have a chance to clean up if TimerUtil.destroy() is called.

TimerTasks run by TimerUtil should have a chance to clean up if TimerUtil.destroy() is called. ---------------------------------------------------------------------------------------------- Key: JBREM-676 URL: http://jira.jboss.com/jira/browse/JBREM-676 Project: JBoss Remoting Issue Type: Task Security Level: Public(Everyone can see) Affects Versions: 2.2.0.Alpha6 Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.Alpha6 org.jboss.remoting.ConnectionValidator is being changed so that it creates a client invoker one time in start() and destroys it in stop(), instead of recreating it for each ping. But it runs in org.jboss.remoting.util.TimerUtil's Timer, and if TimerUtil.destroy() were called, ConnectionValidator.stop() would never get called. Comment from Tom Elrod: "... the Client that created the ConnectionValidator would be out in the cold if someone were to destroy() the TimerUtil since the ConnectionValidator would still be there, just doing nothing (and Client would be unaware that ConnectionValidator is no longer checking for the server to be down). ...Hopefully no one would do that in code."