Bug 1306893

Summary:	[Migration] Document Client Configuration to connect to JBoss's MBean server via JMX
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Brad Maxwell <bmaxwell>
Component:	Documentation	Assignee:	eap-docs <eap-docs>
Status:	CLOSED EOL	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4.6	CC:	eap-docs, sfolkwil
Target Milestone:	---	Keywords:	Documentation
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1306892	Environment:
Last Closed:	2019-08-19 12:47:10 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1306892
Bug Blocks:

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: