Local JMX managed server #275
Merged
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
jmazzitelli
force-pushed
the
local-jmx-managed-server
branch
2 times, most recently
from
bf116f2
to
6cfc0b0
Compare
…over jolokia if you are monitoring the same VM as where the agent is installed
jmazzitelli
force-pushed
the
local-jmx-managed-server
branch
from
6cfc0b0
to
a2f6113
Compare
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.
This adds a new local-jmx managed server so you can monitor JMX from within the same VM as where the agent is running without going over Jolokia REST.
NOTE: this is based on the PR#274 branch