[
https://issues.jboss.org/browse/WFLY-1146?page=com.atlassian.jira.plugin....
]
Darran Lofthouse commented on WFLY-1146:
----------------------------------------
It sounds like you are fixing a problem you have not described here.
Selecting the local process jconsole can connect to JMX - what can not be achieved is an
automatic connection of the CLI integration which as I have stated on other issues my
opinion is that if a user has chosen to connect locally then we should not be creating a
TCP connection ourselves.
{quote}I don't see how this would break non-local authentication.{quote} By supplying
the remoting-jmx URL in this way and selecting the local process the user has no
opportunity to enter a username and password.
Export remoting-JMX address via JVM instrumentation buffer
----------------------------------------------------------
Key: WFLY-1146
URL:
https://issues.jboss.org/browse/WFLY-1146
Project: WildFly
Issue Type: Feature Request
Components: JMX
Reporter: James Livingston
Assignee: Darran Lofthouse
Fix For: 8.0.0.Alpha3
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