[jboss-jira] [JBoss JIRA] Commented: (JBREM-1176) Fix classloader leak caused by client invoker destruction delay facility

[Ron Sigal (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBREM-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12503069#action_12503069 ] 

Ron Sigal commented on JBREM-1176:
----------------------------------

org.jboss.remoting.Client now keeps a counter of the active Clients which are configured with "invokerDestructionDelay" greater than zero.  When the first such Client is created, a java.util.Timer is created, and when the count goes back to 0, the Timer is destroyed.

Testing:

* org.jboss.test.remoting.invoker.testStaticTimer() has been adjusted to account for the fact that the Timer can be created, destroyed, and recreated.

* The classloader leak described in JBPAPP-3193 disappears with this change.

> Fix classloader leak caused by client invoker destruction delay facility
> ------------------------------------------------------------------------
>
>                 Key: JBREM-1176
>                 URL: https://jira.jboss.org/jira/browse/JBREM-1176
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.3.SP1, 2.5.2.SP1 (Flounder)
>            Reporter: Ron Sigal
>            Assignee: Ron Sigal
>             Fix For: 2.2.3.SP2, 2.5.2.SP2 (Flounder)
>
>
> This issue was turned up by https://jira.jboss.org/jira/browse/JBPAPP-3193 "Regression in EAP 4.x testsuite in Ejb3ClassloaderLeakUnitTestCase".  The problem is that org.jboss.remoting.Client creates a static java.util.Timer which is never deleted.

-- 
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