[jboss-remoting-issues] [JBoss JIRA] Commented: (JBREM-1083) Each Client creates a new invokerDestructionTimer
[
https://jira.jboss.org/jira/browse/JBREM-1083?page=com.atlassian.jira.plu...
]
Ron Sigal commented on JBREM-1083:
----------------------------------
Made invokerDesctructionTimer and invokerDestructionTimerLock statice. Also, made
reference to invoker in InvokerDesctructionTimerTask a WeakReference.
Unit test. Added testStaticTimer() to
org.jboss.test.remoting.invoker.ClientInvokerDelayedDestructionTestCase.
Waiting for results in hudson.
Each Client creates a new invokerDestructionTimer
-------------------------------------------------
Key: JBREM-1083
URL: https://jira.jboss.org/jira/browse/JBREM-1083
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.5.0.SP2 (Flounder)
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.5.0.SP3 (Flounder)
When the parameter "invokerDestructionDelay" is greater than 0,
org.jboss.remoting.Client.disconnect() creates a new TImer. There should be one static
Timer.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira