[ https://issues.jboss.org/browse/WFLY-7520?page=com.atlassian.jira.plugin.... ] Gunther v. Wolffersdorff updated WFLY-7520: ------------------------------------------- Steps to Reproduce: These steps work fine using Wildfly 8.2.0.Final and does not work anymore using Wildfly 10.1.0.Final: {code} cd WF_HOME bin\add-user.bat -a monitor monitor {code} in other window start default domain configuration: {code} bin\domain.bat {code} via CLI do these config changes {code} bin\jboss-cli.bat --connect /profile=full/subsystem=jmx/remoting-connector=jmx:add /profile=full/subsystem=jmx/remoting-connector=jmx:write-attribute(name=use-management-endpoint, value=false) /server-group=main-server-group:reload-servers {code} Now you should be able to connect to server-one with VisualVM by *service:jmx:http-remoting-jmx://127.0.0.1:8080* as user *monitor*. Again this works fine using Wildfly 8.2.0.Final and does not work anymore with Wildfly 10.1.0.Final. These steps are for simplification purposes. Also we cannot monitor a domain server in case of different master and slave hosts. was: These steps work fine using Wildfly 8.2.0.Final and does not work anymore using Wildfly 10.1.0.Final: {code} cd WF_HOME bin\add-user.bat -a monitor monitor {code} in other window start default domain configuration: {code} bin\domain.bat {code} via CLI do these config changes {code} bin\jboss-cli.bat --connect /profile=full/subsystem=jmx/remoting-connector=jmx:add /profile=full/subsystem=jmx/remoting-connector=jmx:write-attribute(name=use-management-endpoint, value=false) /server-group=main-server-group:reload-servers {code} Now you should be able to connect to server-one with VisualVM by service:jmx:http-remoting-jmx://127.0.0.1:8080 as user monitor. Again this works fine using Wildfly 8.2.0.Final and does not work anymore with Wildfly 10.1.0.Final. -- This message was sent by Atlassian JIRA (v7.2.3#72005)