Bug 1306892 - Document Client Configuration to connect to JBoss's MBean server via JMX
Summary: Document Client Configuration to connect to JBoss's MBean server via JMX
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Documentation
Version: 6.4.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Christian Huffman
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1306893
TreeView+ depends on / blocked
 
Reported: 2016-02-12 03:04 UTC by Brad Maxwell
Modified: 2019-09-12 09:55 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1306893 (view as bug list)
Environment:
Last Closed: 2019-01-30 19:49:06 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 149973 0 None None None 2016-02-12 03:05:13 UTC
Red Hat Knowledge Base (Solution) 443033 0 None None None 2016-02-12 03:04:41 UTC

Description Brad Maxwell 2016-02-12 03:04:42 UTC 
Document URL: 

Section Number and Name: 

Describe the issue: 

How to configure a JMX client to connect to JBoss's MBean Server via JMX

jconsole is one tool which connects to JBoss's JMX MBean Server
$JBOSS_HOME/bin/jconsole.sh / $JBOSS_HOME/bin/jconsole.bat

There are some 3rd party tools which are used for monitoring which use JMX to connect to a JBoss instance.

Also, custom applications can use the JMX API to connect JBoss's MBean service via JMX

Suggestions for improvement: 

Additional information:
Comment 1 Christian Huffman 2019-01-30 19:49:06 UTC 
I'm closing this issue out due to age. If it persists, file a corresponding JIRA.
Note You need to log in before you can comment on or make changes to this bug.