You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@excalibur.apache.org by "Shash Chatterjee (JIRA)" <de...@excalibur.apache.org> on 2005/04/16 17:28:02 UTC

[jira] Closed: (EXLBR-20) org.apache.avalon.excalibur.thread.impl.DefaultThreadPool is not disposed properly.

     [ http://issues.apache.org/jira/browse/EXLBR-20?page=history ]
     
Shash Chatterjee closed EXLBR-20:
---------------------------------


Will be released with version 2.1

> org.apache.avalon.excalibur.thread.impl.DefaultThreadPool is not disposed properly.
> -----------------------------------------------------------------------------------
>
>          Key: EXLBR-20
>          URL: http://issues.apache.org/jira/browse/EXLBR-20
>      Project: Excalibur Components
>         Type: Bug
>   Components: Thread
>     Reporter: Pawel Stawicki
>     Assignee: Shash Chatterjee
>     Priority: Minor

>
> DefaultThreadPool extends ThreadGroup. When it is created and added to parent ThreadGroup, ThreadGroup holds reference to it. When dispose is called, parent ThreadGroup still has reference to it and garbage collector can not collect it. It causes memory leak.
> This can be solved by calling destroy() in dispose method.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
For additional commands, e-mail: dev-help@excalibur.apache.org