Java Agent

The Java Agent monitors various Java Runtime Environments. It is loaded by a JVM at startup if configured to do so according the configuration set using a JVM command line option.

See Java Agent configuration to learn how to configure the Agent.


The Java Agent uses the following sensors:

Category Sensor Classic Agent OneAgent
Client AWT Yes No
Components EJB Invocation Yes No
Database JDBC Yes Yes
Exceptions Java Exceptions Yes Yes
Frameworks Hibernate Yes No
Struts Yes No
Logging Java Logging Yes Yes
Mainframe CICS/IMS Gateways Yes Yes
Management JMX MBean Server Yes No
Messaging AMQP Yes No
AMQP Receive Entry Point Yes No
JBoss ESB Tagging Yes No
JMS Yes No
JMS Receive Entry Point Yes No
MQSeries Yes No
MQSeries Receive Entry Point Yes No
Mule Tagging Yes No
Tibco Messaging Yes No
Naming services JNDI Yes No
NoSQL Cassandra Yes No
MongoDB Yes No
Threads Executor Tagging Yes Yes
Thread Start Tagging Yes Yes
Remoting Remote Method Invocation (RMI) Yes No
Thrift Tagging Yes No
Test Frameworks Java Tests Yes No
Transactions JTA Yes No
XA Yes No
Web Requests Java Web requests Yes No
Servlets Yes Yes
User Experience Yes No
Web services Java Web Services Yes No


Be aware that:

  • Not all features/sensors available in Classic Agent are already available in the OneAgent for AppMon
  • Features/Sensors known from Classic Agent can behave differently
  • Some features may be still in development


To use OneAgent in AppMon 2017 May, install Classic Agents first then roll them out to the OneAgent. No additional configuration needed. Before you switch to OneAgent, double check your major requirements with the available feature set.


Feature Classic Agent OneAgent
Hot Sensor Placement Yes No
JMX Measures Yes No
Class Browser Yes No
Decompilation Yes No
Memory Dump Yes No