Page History

...

The deployer tool, the GShell deployer commands, and other command line tools can be configured to use the secure JMX server. Please see Tools and commands for more information.

Disable non-secure JMX server

The insecure JMX server can be turned off by modifying the <geronimo_home>/var/config/config.xml configuration file. Edit the <geronimo_home>/var/config/config.xml configuration file and add load="false" attribute to the following entires:

1. <gbean name="JMXService">
2. <module name="org.apache.geronimo.configs/clustering//car">
3. <module name="org.apache.geronimo.configs/tomcat6-clustering-builder-wadi//car"
   
   

   Note
   Adding load="false" attribute to the second entry will disable the clustering support in Geronimo. Right now, the clustering support requires the insecure JMX server to be running. If you need the clustering support, the insecure JMX server cannot be disabled.

Connect the Geronimo with JConsole

• Startup the server with updated config.xml file;
• export GERONIMO_HOME with actual value;
• Start JConsole with following command line:

  Code Block
  jconsole -J-Djavax.net.ssl.keyStore=$GERONIMO_HOME/var/security/keystores/geronimo-default -J-Djavax.net.ssl.keyStorePassword=secret -J-Djavax.net.ssl.trustStore=$GERONIMO_HOME/var/security/keystores/geronimo-default -J-Djavax.net.ssl.trustStorePassword=secret

• In the New Connection dialog, enter the JMX URL as service:jmx:rmi:///jndi/rmi://localhost:1099/JMXSecureConnector, Username as system and Password as manager. Click OK