|Configure log level||Administering the Apache Geronimo Server||Configuring a remote Apache HTTP server|
Starting 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 start the org.apache.geronimo.framework/jmx-security//car module using the Admin Console or the deployer tool. For example:
<geronimo_home>/bin/deploy -u system -p manager start jmx-security
The secure JMX server will be running on port 9998.
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:
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
JConsole is a Java Management eXtension (JMX) compliant GUI tool that can be used to connect to a running Geronimo server instance. In JConsole, you will be able to monitor the JVM memory usage, threads stack trace, loaded classes and VM information as well as Geronimo MBeans. To securely connect to the JMX server on local Geronimo, do as followed:
- Startup the server with updated
- export GERONIMO_HOME with actual value;
- Start JConsole with following command line:
- In the New Connection dialog, enter the JMX URL as
service:jmx:rmi:///jndi/rmi://localhost:1099/JMXSecureConnector, Username as
systemand Password as
manager. Click Connect. See Configuring SSL client authentication about instructions for Geronimo 2.1.5.