[
https://issues.jboss.org/browse/AS7-6950?page=com.atlassian.jira.plugin.s...
]
James Livingston commented on AS7-6950:
---------------------------------------
https://github.com/doctau/jboss-as/tree/AS7-6950 contains a PoC implementation of this.
Currently it hard-codes localhost:9999 as the address, because
DelegatingRemotingConnectorServer.getAddress() always returns null. Using this, you can
use the local process list in JConsole to connect to JBoss without manually entering the
address.
I'm not sure what the correct way of the JMX subsystem finding out the address it
operates on, and the from the comments method author didn't know at the time either.
Export remoting-JMX address via JVM instrumentation buffer
----------------------------------------------------------
Key: AS7-6950
URL:
https://issues.jboss.org/browse/AS7-6950
Project: Application Server 7
Issue Type: Feature Request
Components: JMX
Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
Reporter: James Livingston
Assignee: Stuart Douglas
Currently to connect to the AS with JConsole you need to manually enter the
service:jmx:remoting-jmx:// address. When the local process connection is used, it
retrieves the connection address via the Sun JDK management instrumentation buffer.
The exported address can be set via sun.management.ConnectorAddressLink.export(), and
doing that would allow JConsole to connect without typing in the address (although still
obviously require the jars to be on the classpath).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira