-
Bug
-
Resolution: Done
-
Major
-
7.3.0.GA
-
None
Performance Tuning Guide 2.1. Configuring JBoss EAP for Remote Monitoring Connections
The documentation describes the following steps, but in EAP 7.1 and later, this procedure does not work with the connection error.
For a Managed Domain Host: ... /profile=full/subsystem=jmx/remoting-connector=jmx:add(use-management-endpoint=false) /socket-binding-group=full-sockets/socket-binding=remoting:add(port=4447) /profile=full/subsystem=remoting/connector=remoting-connector:add(socket-binding=remoting,security-realm=ApplicationRealm)
Instead of using the legacy security module for authentication, you can connect using Elytron as below:
/profile=full/subsystem=jmx/remoting-connector=jmx:add(use-management-endpoint=false) /socket-binding-group=full-sockets/socket-binding=remoting:add(port=4447) -/profile=full/subsystem=remoting/connector=remoting-connector:add(socket-binding=remoting,security-realm=ApplicationRealm) +/profile=full/subsystem=remoting/connector=remoting-connector:add(socket-binding=remoting,sasl-authentication-factory=application-sasl-authentication)
- is cloned by
-
JBEAP-22915 [GSS](7.4.z.)Performance Tuning Guide: unable to connect jconsole to EAP domain servers
- Closed
- is related to
-
JBEAP-8901 jconsole not able to connect to EAP domain servers from remote system
- Closed
- links to