You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "clebert suconic (JIRA)" <ji...@apache.org> on 2017/08/31 19:12:46 UTC

[jira] [Closed] (ARTEMIS-874) ThreadGroup memory leak

     [ https://issues.apache.org/jira/browse/ARTEMIS-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

clebert suconic closed ARTEMIS-874.
-----------------------------------

> ThreadGroup memory leak
> -----------------------
>
>                 Key: ARTEMIS-874
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-874
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 1.5.0
>            Reporter: Damien Hollis
>             Fix For: 2.1.0
>
>
> Each ActiveMQConnection has a failoverListenerExecutor, which is initialized using the code 
> {code:java}
> Executors.newFixedThreadPool(1, ActiveMQThreadFactory.defaultThreadFactory());
> {code}
> Which creates a new ActiveMQThreadFactory and the factory has a ThreadGroup.  When ThreadGroups are created, they are added to an array on their parent ThreadGroup.  In our testing, the array of ThreadGroups just keeps growing as we keep creating ActiveMQConnections.  The problem seems to be that nobody is destroying the ThreadGroups (ThreadGroup.destroy()).  Note: the ActiveMQConnection etc are all cleaned up correctly.  
> I've managed to workaround this issue by caching the ActiveMQConnection but in some environments this might not be possible.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)