]
Ron Sigal updated JBREM-1111:
-----------------------------
Fix Version/s: (was: 2.4.0.Beta1 (Pinto))
Affects Version/s: (was: 2.4.0.Beta1 (Pinto))
(was: 2.2.2.GA_CP01)
(was: 2.2.2.SP2)
CLONE [JBREM-851] - In LeasePinger replace Timer if it has shut down
--------------------------------------------------------------------
Key: JBREM-1111
URL:
https://jira.jboss.org/jira/browse/JBREM-1111
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.5.0.SP2 (Flounder) , 2.2.2.SP11
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.5.0.SP3 (Flounder), 2.2.2.SP12
Description from JBREM-851:
When all of the TimerTasks running in a java.util.TimerTask have shut down, the TImer
will also shut down, at which point it will accept no more TimerTasks. There are places
in Remoting where there should be a test which will create a new Timer the attempt to
schedule a TimerTask results in an exception.
Two places the problem exists:
1. org.jboss.remoting.LeasePinger, and
2. org.jboss.remoting.util.TimerUtil.
A similar problem is described in JBREM-748 "BisocketClientInvoker should guard
agains scheduling on an expired Timer"
Reported by James on Remoting forum.
It turns out I thought fixing LeasePinger was unnecessary since each LeasePinger gets its
own Timer, but that's JUST NOT TRUE.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: