activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-874) ThreadGroup memory leak
Date Fri, 05 May 2017 18:51:04 GMT

    [ https://issues.apache.org/jira/browse/ARTEMIS-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998779#comment-15998779
] 

ASF GitHub Bot commented on ARTEMIS-874:
----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/activemq-artemis/pull/1255


> 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
>
> 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.3.15#6346)

Mime
View raw message