[REMJMX-160] Mark the remoting-jmx thread group as a daemon thread group #38
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
A daemon thread group is automatically destroyed when its last thread is stopped or its last thread group is destroyed. This can avoid a memory leak by retaining many ThreadGroup objects when a JMX client repeats creating and closing a connection many times.
msfm
changed the title
|
Is this one really required, the 1.1 branch has not undergone any maintenance for almost five years now. |
|
I think this is required because the original issue was reported against EAP 6.4 which comes with remoting-jmx 1.1 branch. (The latest CP21 comes with remoting-jmx 1.1.3.Final). I've just added the BZ information to the first comment. |
|
Ok I will see if we get sufficient ACKs to merge. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1697284
JIRA: https://issues.jboss.org/browse/REMJMX-160
Upstream: #36
3.0.x: #37