[
http://jira.jboss.com/jira/browse/JBREM-662?page=comments#action_12351171 ]
Ron Sigal commented on JBREM-662:
---------------------------------
I've changed ConnectionValidator so that it creates a client invoker one time in
start() and destroys it in start(). A complication, pointed out by Tom Elrod, is that the
client invoker could leak if stop() doesn't run for some reason. In particular,
ConnectionValidator runs on the TimerUtil Timer, and if TimerUtil.destroy() were called,
ConnectionValidator.stop() wouldn't get called.
JBREM-676 was created to fortify TimerUtil so that destroy() will call stop() on any
TimerTask that implements the new org.jboss.remoting.util.StoppableTimerTask interface.
That has been done, and ConnectionValidator has been updated to implement
StoppableTimerTask.
New unit test:
org.jboss.test.remoting.connection.ConnectionValidatorCachedInvokerTestCase.
Failed ClientInvoker not cleaned up properly
--------------------------------------------
Key: JBREM-662
URL:
http://jira.jboss.com/jira/browse/JBREM-662
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.2.0.Alpha6
Reporter: Ovidiu Feodorov
Assigned To: Ron Sigal
Fix For: 2.2.0.Alpha6
--
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