[
https://issues.jboss.org/browse/JGRP-2244?page=com.atlassian.jira.plugin....
]
Bela Ban resolved JGRP-2244.
----------------------------
Resolution: Done
Added methods to get and set both the internal pool itself and the associated thread pool
factory. You may want to use {{setInternalThreadPool()}} directly...
Use of TP.internal_pool can result in classloader leaks
-------------------------------------------------------
Key: JGRP-2244
URL:
https://issues.jboss.org/browse/JGRP-2244
Project: JGroups
Issue Type: Bug
Affects Versions: 4.0
Reporter: Paul Ferraro
Assignee: Bela Ban
Fix For: 4.0.10
As of JGroups 4.0, the ThreadFactory of the internal thread pool cannot be overridden.
Consequently, there is no mechanism to associate newly spawned threads with a specific
classloader. If an application thread results in the spawning of an thread in this
internal pool [1], the application class loader can leak to other threads used the the
JGroups channel.
[1]
https://github.com/belaban/JGroups/blob/master/src/org/jgroups/protocols/...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)