Novaordis-jmx: Difference between revisions
| Line 23: | Line 23: | ||
=cljmx User Manual= | =cljmx User Manual= | ||
The connection URL for a JBoss instance running in standalone mode is "jmx://<server-host-address>:9999", because a standalone JBoss instance exposes the JMX bus over the management inferface. For a JBoss server instance running in domain mode, the connection URL is jmx://<server-host-address>:4447. 4447 should be replaced with whatever port the Remoting subsystem is listening on, in case it was changed. This is because a JBoss server instance running in domain mode does not start a management interface, and exposes its JMX bus over its remoting connector. Additionally, the server instance has to be configured to expose the JMX bus over its remoting connector by setting <remoting-connector use-management-endpoint="false"/> in the remoting subsystem configuration of the corresponding server profile. | The connection URL for a JBoss instance running in standalone mode is "jmx://<server-host-address>:9999", because a standalone JBoss instance exposes the JMX bus over the management inferface. For a JBoss server instance running in domain mode, the connection URL is jmx://<server-host-address>:4447. 4447 should be replaced with whatever port the Remoting subsystem is listening on, in case it was changed. This is because a JBoss server instance running in domain mode does not start a management interface, and exposes its JMX bus over its remoting connector. Additionally, the server instance has to be configured to expose the JMX bus over its remoting connector by setting <remoting-connector use-management-endpoint="false"/> in the remoting subsystem configuration of the corresponding server profile. If the remoting interface is secured, a user with proper credentials from the security realm associated with the remoting subsystem has to be used. More details are available here [[JMX_Access_to_Domain_Mode_EAP_6_Server_Node|JMX Access too Domain Mode EAP 6 Server Node]]. | ||
cljmx [--username=''<valid-application-realm-user>''] [''--password=<password>''] jmx://''<server-node-host-address>'':9999|4447 | cljmx [--username=''<valid-application-realm-user>''] [''--password=<password>''] jmx://''<server-node-host-address>'':9999|4447 | ||
Latest revision as of 07:59, 8 July 2017
Internal
Overview
Provides novaordis-jmx.jar, which is a library, and a command line utility that can be used to explore a remote JMX bus.
cljmx localhost:9999
See cljmx User Manual for more details.
The current version (1.1.x) is built by declaring a static dependency of a specific JBoss version at compile time and embedding the dependencies within the artifact.
GitHub
Accessing WildFly JMX Bus Remotely with novaordis-jmx
cljmx User Manual
The connection URL for a JBoss instance running in standalone mode is "jmx://<server-host-address>:9999", because a standalone JBoss instance exposes the JMX bus over the management inferface. For a JBoss server instance running in domain mode, the connection URL is jmx://<server-host-address>:4447. 4447 should be replaced with whatever port the Remoting subsystem is listening on, in case it was changed. This is because a JBoss server instance running in domain mode does not start a management interface, and exposes its JMX bus over its remoting connector. Additionally, the server instance has to be configured to expose the JMX bus over its remoting connector by setting <remoting-connector use-management-endpoint="false"/> in the remoting subsystem configuration of the corresponding server profile. If the remoting interface is secured, a user with proper credentials from the security realm associated with the remoting subsystem has to be used. More details are available here JMX Access too Domain Mode EAP 6 Server Node.
cljmx [--username=<valid-application-realm-user>] [--password=<password>] jmx://<server-node-host-address>:9999|4447
cljmx jmx://<valid-application-realm-user>:<password>@<server-node-host-address>:<jmx-port>
> help A command line JMX browser. Use it to navigate the MBeanServer domain/MBean hierarchy as you would navigate a filesystem. Commands: cd - navigate to a domain or MBean ls - list the content of a domain or an MBean pwd - show the location in the hierarchy