THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Before CXF 3.4.0, the following options were also available. From CXF 3.4.0, these options are removed, as there is no real advantage to creating a custom JMX local Connector. Local JMX monitoring can be done using standard tools, and remote JMX monitoring is done using the standard JVM JXM options (see below).
Name | Value | Default |
|---|---|---|
createMBServerConnectorFactory deprecated | If true, a connector is created on the MBeanServer. | true |
threaded deprecated | Determines if the creation of the MBean connector is performed in this thread or in a separate thread. Only relevant if createMBServerConnectorFactory is true. | false |
daemon deprecated | Determines if the MBean connector creation thread is marked as a daemon thread or not. Only relevant if createMBServerConnectorFactory is true. | false |
JMXServiceURL deprecated | The URL of the connector to create on the MBeanServer. Only relevant if createMBServerConnectorFactory is true. | service:jmx:rmi:///jndi/rmi://localhost:9913/jmxrmi |
| environment deprecated | This is a map that is used to configure the RMI environment. | None |
The MBean instrumentation provided by the above configuration will provide generic information about the WSDL supported by the web service as well as web service administration commands. To see performance metrics of the SOAP call processing, further configuration is required – these are disabled by default to avoid unnecessary runtime overhead.
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
<cxf:bus bus="cxf">
<cxf:properties>
<entry key="bus.jmx.enabled" value="true" />
<entry key="bus.jmx.JMXServiceURL" value="service:jmx:rmi:///jndi/rmi://localhost:9914/jmxrmi" />
<entry key="bus.jmx.usePlatformMBeanServer" value="true" />
</cxf:properties>
</cxf:bus>
|
...
| Anchor | ||||
|---|---|---|---|---|
|
Remote access
Remove Remote access to JMX is configured using the standard JVM JMX options. For example if you want to enable remote access without enabling TLS, but using authentication against local access and password files:
| Code Block |
|---|
-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=9913 -Dcom.sun.management.jmxremote.authenticatessl=false -Djava.rmi.server.hostname=localhost -Dcom.sun.management.jmxremote.access.ssl=false -Djava.rmi.server.hostname=localhostfile=conf/jmx.access -Dcom.sun.management.jmxremote.password.file=conf/jmx.password |
Then you can connect using jconsole specifying either of the following for the remote process, and supplying a username + password to match what you have configured:
- localhost:9913
- service:jmx:rmi:///jndi/rmi://localhost:9913/jmxrmi
...