[
http://jira.jboss.com/jira/browse/JBREM-748?page=all ]
Ron Sigal updated JBREM-748:
----------------------------
Fix Version/s: 2.4.0.Beta1 (Pinto)
Added fix version 2.4.0.Beta1 - see JBREM-975 "Make sure all fixes on 2.2 branch are
applied to 2.x branch".
BisocketClientInvoker should guard agains scheduling on an expired
Timer
------------------------------------------------------------------------
Key: JBREM-748
URL:
http://jira.jboss.com/jira/browse/JBREM-748
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.2.0.SP4, 2.4.0.Beta1 (Pinto)
In two places, org.jboss.remoting.transport.bisocket.BisocketClientInvoker schedules a
PingTimerTask on the Timer referenced by the static variable timer. The problem is that
if the Timer has been around for a while and all of its tasks have completed, it could
have entered a state in which in can no longer schedule new tasks.
--
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