activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Justin Bertram <>
Subject Re: ARTEMIS-874 ThreadGroup memory leak
Date Fri, 05 May 2017 02:47:30 GMT
I'm actually not sure why ActiveMQThreadFactory needs a thread group at all. As long as the
threads are named appropriately I think there doesn't need to be a group and that would solve
this leak. Otherwise we'd have to figure out a way to call destroy() on the group when pool
is shutdown and that isn't obvious.


----- Original Message -----
From: "Denis V. Kirpichenkov" <>
Sent: Thursday, May 4, 2017 12:48:43 PM
Subject: ARTEMIS-874 ThreadGroup memory leak

Hello, All!

Recently I faced with a memleak described in And my question is 
why does  ActiveMQThreadFactory.defaultThreadFactory() create its own 
ThreadGroup? May be it is fine to work without it?

View raw message