Bug 1306893 - [Migration] Document Client Configuration to connect to JBoss's MBean server via JMX
[Migration] Document Client Configuration to connect to JBoss's MBean server ...
Status: NEW
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Documentation (Show other bugs)
6.4.6
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: David Michael
: Documentation
Depends On: 1306892
Blocks:
  Show dependency treegraph
 
Reported: 2016-02-11 22:07 EST by Brad Maxwell
Modified: 2016-07-03 21:40 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1306892
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 149973 None None None 2016-02-11 22:07 EST
Red Hat Knowledge Base (Solution) 443033 None None None 2016-02-11 22:07 EST

  None (edit)
Description Brad Maxwell 2016-02-11 22:07:52 EST
In JBoss EAP 5 and earlier, the JVM's MBean server was used, in JBoss EAP 6, the client should connect to the JBoss's MBean services via remoting-jmx.

+++ This bug was initially created as a clone of Bug #1306892 +++

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:

Note You need to log in before you can comment on or make changes to this bug.