• JMX MBeans
• JConsole
• JBoss JMX Console

JMX MBeans

Most of functionality provided by GridGain is implemented via Service Provider Interface (SPI) modules. As discussed above there are 6 types of SPIs in GridGain 1.0:

• Communication SPI
• Deployment SPI
• Checkpoint SPI
• Collision SPI
• Event Storage SPI
• Discovery SPI

Every SPI is responsible for providing its own JMX instrumentation (if required). GridGain kernel provides the only JMX Bean that is always available since it is controlled by non-SPI module, namely kernal. Note that all SPI implementations provided by GridGain (those that are shipped with the product) provide JMX instrumentation. Note also that JMX instrumentation provided by built-in SPI modules is intended for basic monitoring and administration purposes - not for programmatic remote control of SPI module.

Here is the list of MBean interfaces for all built-in SPI implementations and kernal:

• Kernal
  • GridKernalMBean
• Checkpoint SPI
  • GridSharedFsCheckpointSpiMBean ^Javadoc
• Collision SPI
  • GridPriorityCollisionSpiMBean ^Javadoc
• Communication SPI
  • GridJgroupsCommunicationSpiMBean ^Javadoc
  • GridJmsCommunicationSpiMBean ^Javadoc
  • GridMailCommunicationSpiMBean ^Javadoc
  • GridTcpCommunicationSpiMBean ^Javadoc
• Deployment SPI
  • GridLocalDeploymentSpiMBean ^Javadoc
  • GridUriDeploymentSpiMBean ^Javadoc
• Discovery SPI
  • GridJbossDiscoverySpiMBean ^Javadoc
  • GridJgroupsDiscoverySpiMBean ^Javadoc
  • GridJmsDiscoverySpiMBean ^Javadoc
  • GridMailDiscoverySpiMBean ^Javadoc
  • GridMulticastDiscoverySpiMBean ^Javadoc
• Event Storage SPI
  • GridMemoryEventStorgeSpiMBean ^Javadoc

JConsole

JConsole is a standard JMX console that ships with JDK starting with version 5. It allows to access JMX instrumentation of the VM itself as well as any user defined MBeans as long as this VM is started with management agent.

To start an application with the management agent for local monitoring, set the com.sun.management.jmxremote system property when you start the application in the command line:

JDK_HOME/bin/java -Dcom.sun.management.jmxremote

where JDK_HOME is the directory containing the JDK.

Windows Domain and JConsole If you are using standard JDK JConsole on Windows you may encounter an undocumented behavior when you cannot locally connect to the JConsole if you logged in into Windows domain. In this case you will need to connect as 'remote'. For more information on troubleshooting see the following link: http://java.sun.com/j2se/1.5.0/docs/guide/management/faq.html

To start JConsole, run

JDK_HOME/bin/jconsole

Note that start scripts shipped with GridGain gridgain.{sh|bat} start GridGain node instance with management agent enabled for local monitoring only. So, when you start GridGain node and run JConsole you will see the following (assuming local ndoe with default configuration):

For more information see "Monitoring and Management Using JMX

JBoss JMX Console

When running within JBoss you can use either JBoss Web Console or JBoss JMX Console that provide similar web-based access to JMX MBeans. When running JBoss locally open your browser and point it to either:

• http://127.0.0.1:8080/jmx-console/ for JMX console
• http://127.0.0.1:8080/web-console/ for full JBoss Web management console