Monitoring your Cluster with JMX

Monitoring is a very important question when you use a cluster. Some of the cluster objects are JMX MBeans.

Add the following parameter to your startup script with Java 5:

set CATALINA_OPTS=\

-Dcom.sun.management.jmxremote \

-Dcom.sun.management.jmxremote.port=%my.jmx.port% \

-Dcom.sun.management.jmxremote.ssl=false \

-Dcom.sun.management.jmxremote.authenticate=false

List of Cluster Mbeans

Name	Description	MBean ObjectName – Engine	MBean ObjectName – Host
Cluster	The complete cluster element	type=Cluster	type=Cluster,host=${HOST}
DeltaManager	This manager control the sessions and handle session replication	type=Manager,context=${APP.CONTEXT.PATH}, host=${HOST}	type=Manager,context=${APP.CONTEXT.PATH}, host=${HOST}
FarmWarDeployer	Manages the process of deploying an application to all nodes in the cluster	Not supported	type=Cluster, host=${HOST}, component=deployer
Member	Represents a node in the cluster	type=Cluster, component=member, name=${NODE_NAME}	type=Cluster, host=${HOST}, component=member, name=${NODE_NAME}
ReplicationValve	This valve control the replication to the backup nodes	type=Valve,name=ReplicationValve	type=Valve,name=ReplicationValve,host=${HOST}
JvmRouteBinderValve	This is a cluster fallback valve to change the Session ID to the current tomcat jvmroute.	type=Valve,name=JvmRouteBinderValve, context=${APP.CONTEXT.PATH}	type=Valve,name=JvmRouteBinderValve,host=${HOST}, context=${APP.CONTEXT.PATH}