Bug 1306893 - [Migration] Document Client Configuration to connect to JBoss's MBean server via JMX
Summary: [Migration] Document Client Configuration to connect to JBoss's MBean server ...
Keywords:
Status: CLOSED EOL
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: eap-docs
QA Contact:
URL:
Whiteboard:
Depends On: 1306892
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-12 03:07 UTC by Brad Maxwell
Modified: 2019-09-12 09:55 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1306892
Environment:
Last Closed: 2019-08-19 12:47:10 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


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

Description Brad Maxwell 2016-02-12 03:07:52 UTC 
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.