ExcerptStarting with Geronimo 2.1.2, Geronimo has a secure JMX server. However, the JMX server is not started by default. To start the secure JMX server, for example connecting the Geronimo with Jconsole, you have to follow the steps below:

Disable non-secure JMX server

1. To disable non-secure JMX server, stop the Geronimo server if it has been started, and modify the config.xml file in the <Geronimo_HOME>/var/config directory, where <Geronimo_HOME> is the installation directory of your Geronimo server.
2. Exclude the following items from the modules pre-configured to get started by adding load="false" to the elements:

   No Format
   <gbean name="JMXService" load="false"> ... <module name="org.apache.geronimo.configs/clustering//car" load="false"> ... <module name="org.apache.geronimo.configs/tomcat6-clustering-builder-wadi//car" load="false">

...

the

...

secure JMX server

...

start the org.apache.geronimo.framework/jmx-security//car module using the Admin Console or the deployer tool. For example:

...

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

Connect the Geronimo with JConsole

...

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/2.1/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.