Filippe,
I added the option you said and reload the servers:
/profile=full/subsystem=jmx/remoting-connector=jmx:add(use-management-endpoint=false)
The options expose-resolved-model and expose-expression-model are
default. However, I still can't connect to slave host. The only
connection that works in slave is when I connect on port 9999 with
address "service:jmx:remoting-jmx:host:9999", but the "jboss.as.*"
MBeans aren't showed.
I tried addresses "service:jmx:remoting-jmx:host:8080" and
"service:jmx:http-remoting-jmx:host:8080" and nothing.
I thought could be the user authentication, so I create the same
user in mgmt-users.properties and application-users.properties but
didn't work.
Did I do anything wrong?
Thanks,
Rodrigo
On 20-01-2016 15:41, Filippe spolti wrote:
This is
switched on by default in standalone mode and accessible over
port 9990 but in domain mode is switched off so needs to be
enabled - in domain mode the port will be the port of the
Remoting connector for the WildFly 8 instance to be monitored.
the jmx subsystem should looks like:
<subsystem xmlns="urn:jboss:domain:jmx:1.3">
<expose-resolved-model/>
<expose-expression-model/>
<remoting-connector
use-management-endpoint="false"/>
</subsystem>
Then use the server's http port to access the jmx.
On 01/20/2016 03:12 PM, Rodrigo Lira
wrote:
Hi,
After install WildFly in standalone mode I can access JMX with JConsole using the address service:jmx:http-remoting-jmx://host:9990, but when I install in domain mode only the domain controller is accessible, I can't connect in host slaves. How do I enable JMX in host slaves?
--
Regards,
--Filippe
_______________________________________________
wildfly-dev mailing list
wildfly-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
_______________________________________________
| Rodrigo Daniel C. Lira
|
Analista de Sistemas - Tribunal de Justiça/PR
|
rodrigo.lira@tjpr.jus.br - (41) 3250-6344