[jboss-jira] [JBoss JIRA] (WFLY-1146) Export remoting-JMX address via JVM instrumentation buffer

[Darran Lofthouse (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Darran Lofthouse resolved WFLY-1146.
------------------------------------

    Fix Version/s: 8.0.0.Alpha3
       Resolution: Rejected


There are two reasons for rejecting this change: -
 1 - It is dependent on an internal sun api which is subject to change and not guaranteed to always be available.
 2 - The moment any authentication other than the local authentication mechanism is in place this prevents a connection to the server as no username or password can be entered.
                
> 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