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
all versions
AppMon Agent
AppMon 2017 May
AppMon Agent
AppMon 2018 April
Client AWT Yes No Yes
Components EJB Invocation Yes No No
Database JDBC Yes Yes Yes
Exceptions Java Exceptions Yes Yes Yes
Frameworks Hibernate Yes No Yes
Struts Yes No Yes
Logging Java Logging Yes Yes Yes
Mainframe CICS/IMS Gateways Yes Yes Yes
Management JMX MBean Server Yes No Yes
Messaging AMQP Yes No Yes
AMQP Receive Entry Point Yes No Yes
JBoss ESB Tagging Yes No Yes
JMS Yes No Yes
JMS Receive Entry Point Yes No Yes
MQSeries Yes No Yes
MQSeries Receive Entry Point Yes No Yes
Mule Tagging Yes No Yes
Tibco Messaging Yes No Yes
Naming services JNDI Yes No No
NoSQL Cassandra Yes No Yes
MongoDB Yes No Yes
Threads Executor Tagging Yes Yes Yes
Thread Start Tagging Yes Yes Yes
Remoting Remote Method Invocation (RMI) Yes No Yes
Thrift Tagging Yes No Yes
Test Frameworks Java Tests Yes No Yes
Transactions JTA Yes No Yes
XA Yes No Yes
Web Requests Java Web requests Yes No Yes
Servlets Yes Yes Yes
User Experience Yes No Yes
Web services Java Web Services Yes No Yes

Agent Platforms

This Agent is available in both agent platforms. Please check the release status of the Agent before switching over as some Agents have BETA status in AppMon 2017 May .

It is recommended to switch over from Classic Agent for following scenarios:

  • To improve Collector scalability
  • To resolve Collector connectivity problems


Feature Classic Agent
all versions
AppMon Agent
AppMon 2017 May
AppMon Agent
AppMon 2018 April
Hot Sensor Placement Yes No Yes
JMX Measures Yes No Yes
Class Browser Yes No Yes
Decompilation Yes No Yes
Memory Dump Yes No Yes 1

1map and collection detection for memory dumps not working