AppDynamics Application Intelligence Platform

3.9.x Documentation

PDFs

Learn by Watching

Doc Maps

Supported Platform Matrix for the Java Agent

This page documents known environments in which the Java Agent has been used to instrument applications. The Java Agent can target specific Java bytecode. This provides wide-ranging flexibility, so if an environment is not listed here, this does not preclude the Java Agent from being able to extract valuable performance metrics. Contact AppDynamics Support or Sales for additional details.

Notes:

  • A dash ("-") in a table cell indicates that this column is not relevant or not supported for that particular environment.
  • In cases where no version is provided, assume that all versions are supported. Contact AppDynamics Support or Sales for confirmation.
  • For environments that  require additional configuration, a separate table describing or linking to configuration information follows the support matrix.
  • For environments supported by AppDynamics End User Monitoring, see Supported Environments and Versions - Web EUM.

JVM Support

These are the known JVM environments in which the Java Agent has been used to instrument applications. 

Vendor

Implementation

Version

Operating System

Object Instance
Tracking

Automatic Leak
Detection

Custom Memory Structures

      Content InspectionAccess TrackingRequires JVM Restart?

Oracle

Java HotSpot

7 Update 45+

Solaris Sparc 64, Windows, Linux

-

-

-

--
Oracle

Java SE
(Standard Edition)
New in 3.9 

8Solaris Sparc 64, Windows, LinuxYesYesYesYesYes

BEA

JRockit

1.5

-

-

Yes

Yes

YesYes
BEAJRockit1.6, 1.7--YesYes--

Oracle

JRockit JVM

28.1+

Linux Intel 64 Windows

-

-

-

--

IBM

JVM

1.5.x, 1.6.x, 1.7.x

-

-

-

-

--

SUN

JVM

1.5, 1.6, 1.7

-

Yes

Yes

Yes

Yes-

Open Source

OpenJDK

1.6

Linux, windows, everywhere

-

Yes

-

--

HP

OpenVMS

-

-

-

-

-

--

Notes:

  • Both JDKs and JREs Supported
  • Object instance tracking, automatic leak detection, and custom memory structure monitoring are not supported with the IBM Java Agent on an IBM JVM. As a workaround, to get automatic leak detection and custom memory structure monitoring, you can use the Java agent for Sun and JRockit JVM on the IBM JVM. However, doing so will likely result in a negative performance impact. In either case, object instance tracking is not supported on IBM JVM's.
  • All JVMs must be restarted after enabling the Automatic Leak Detection feature.
  • For examples of instrumenting new language constructs in Java SE 8, see Instrumenting New Constructs Available in Java 8.

JVM Language Frameworks Support

No additional configuration is required for these frameworks.

Vendor

JVM Language 
Framework

Version

Correlation/
Entry Points

Exit Points

Transports

Notes

Open Source /
Typesafe Reactive Platform

Akka Actor

2.1 - 2.3

Yes

Yes

Netty

Remoting exit/entry supported.
Persistence (experimental module in v2.3) is not currently supported.

Open Source

Groovy

-

Yes

Yes

 

 

Open Source /
Typesafe Reactive Platform

Play for Scala

2.1 - 2.3

Yes

-

HTTP over Netty

Includes framework specific entry points
Open Source /
Typesafe Reactive Platform
Spray.io-NoNoNoCurrently not supported

Pivotal

Grails

-

-

-

-

 

The Typesafe Reactive Platform is a JVM-based runtime and collection of tools used to build reactive applications. This includes ScalaPlayAkka, and Spray.io

Application Servers

These are the known application server environments in which the Java Agent has been used to instrument applications. Some require additional configuration. Click the link on the server or OSGi Runtime name in the following support matrix for information about additional configuration required or related configuration topics. Application servers are usually found by the Java Agent as an entry point.

Vendor

Application Server / 
OSGi Runtime

Version

SOA Protocol

RMI Supported

JMX

Entry Points

Apache

Felix

-

-

-

-

Yes

Apache

Sling

-

-

-

-

Yes

Apache

Tomcat

5.x, 6.x,7.x

-

-

Yes

 

Apache

Resin

1.x - 4.x

-

-

-

-

Adobe

Cold Fusion

8.x, 9.x

-

No

-

 Yes

 

Equinox

-

-

-

-

Yes

Eclipse

Jetty

6.x, 7.x

-

-

-

-

IBM

InfoSphere

8.x

-

-

-

Yes

IBM

WebSphere  

6.1

JAX-WS

-

-

Yes

IBM

WebSphere  

7.x

JAX-WS

Yes, detect and correlate

Yes for WebSphere PMI

Yes

IBMWebSphere8.xJAX-WSYes, detect and correlate-Yes

Open Source

Liferay Portal

-

-

-

-

-

 

GlassFish Enterprise Server

2.x

-

-

Yes

Yes

Oracle

GlassFish Server and 
GlassFish Server Open Source Edition

3.1+

-

-

Yes for AMX

Yes

Oracle and BEA

WebLogic Server

9.x+

JAX-WS

Yes, detect and correlate for 10.x

Yes

Yes

New in 3.9.7 TibcoActiveMatrix BusinessWorks Service Engine5.7---Yes
 

Application Server (OC4J)

-

-

Yes, detect and correlate for 10.x

-

Yes

-

Grails, with Tomcat 7.x, Glassfish v3, 
Weblogic 12.1.1 (12c)

-

-

-

-

 

-

JBoss Server

7+

-

-

-

Yes

-

JBoss Server  

4.x, 5.x

-

Yes, detect and correlate

-

Yes

 JBoss AS6.x, 7.x standalone)    
 JBoss EAP6.11, 6.2.0    

 

Application Server Configuration

For application server environments that require additional configuration, this section provides some information and links to topics that help you configure the environment. Environments in the Application Server Support table that require additional configuration, link to the configuration table below. 

Application ServerTopics for Required and Optional Configuration

Apache Felix

Apache Sling
Apache Tomcat
Apache Resin
Apache Cold Fusion 

Configuration is required for transaction discovery, see 

Equinox
Eclipse Jetty
IBM InfoSphere

IBM WebSphere

Sun GlassFish Enterprise Server

GlassFish JDBC connection pools can be manually configured using MBean attributes and custom JMX metrics

Oracle GlassFish Server

including GlassFish Server Open Source Edition

Oracle and BEA WebLogic Server
Tibco ActiveMatrix BusinessWorks Service
JBoss Server

Message Oriented Middleware Support

These are the known message oriented middleware environments in which the Java Agent has been used to instrument applications. Some require additional configuration. Click the link on the messaging server name in the following support matrix for information about additional configuration required or related configuration topics. Message oriented middleware servers are usually found by the Java Agent as an entry point.

Vendor

Messaging Server

Version

Protocol

Correlation/Entry Points

Exit Points

JMX

Apache

ActiveMQ

5.x+

JMS 1.x

Yes

Yes

Yes

Apache

ActiveMQ

5.x+

STOMP

No

-

Yes

Apache

ActiveMQ

5.8.x+

AMQP 1.0

No

-

Yes

Apache

ActiveMQ

5.x+

SOAP

Yes

-

Yes

Apache

Axis

1.x, 2.x

JAX-WS

Yes

Yes

-

Apache

Apache CXF

2.1

JAX-WS

Yes

Yes

-

Apache

Synapse

2.1

HTTP

Yes

Yes

-

Fiorano

Fiorano MQ

 

-

-

-

-

IBM

IBM MQ

6.x, 7.x

-

-

-

-

IBM

IBM Web Application Server (WAS)

6.1+, 7.x

Embedded JMS

-

Yes

-

IBM

IBM WebSphere MQ

-

JMS

Yes

Yes

-

 

JBoss MQ

4.x

-

-

-

Yes

JBoss

JBoss Messaging

5.x

-

-

-

Yes

JBoss

HornetQ

-

-

-

-

Yes

 

Open MQ

-

-

-

-

-

Mulesoft

Mule ESB

3.4

HTTP

Yes

Yes

-

OracleJave Message Service
New in 3.9 
2.0JMScorrelation of the listener
is disabled by default 
Yes 

Oracle

Oracle AQ

-

JMS

-

Yes

-

Oracle / BEA

WebLogic

9.x+

JMS 1.1

Yes

Yes

Yes

Progress

SonicMQ

-

-

-

-

-

Pivotal

RabbitMQ

-

HTTP

-

Yes

-

Rabbit

RabbitMQ Spring Client

-

-

Yes

Yes

-

Spring

Spring Integration

2.2.0

JMS

Yes

Yes

Yes

Message Oriented Middleware Configuration

For message oriented middleware environments that require additional configuration, this section provides some information and links to topics that help you configure the environment.  Environments in the Message Oriented Middleware Support table that require additional configuration, link to the configuration table below. 

Messaging ServerTopics for Required and Optional Configuration
Apache ActiveMQ
Apache Axis

Default exclude rules exist for Apache Axis, Axis2, and Axis Admin Servlets.  See also,

Apache Synapse
IBM MQ 

No additional configuration is required.

See also, Default Backends Discovered by the App Agent for Java

IBM Web Application Server

No additional configuration is required. See also, 

IBM WebSphere MQ
Mule ESB
BEA WebLogic
Pivotal RabbitMQ

No additional configuration is required. See also,

RabbitMQ Spring Client

No addition configuration is required, See also,

Spring Integration

JDBC Drivers and Database Servers Support

These are the known JDBC driver and database server environments in which the Java Agent has been used to instrument applications. AppDynamics can follow transactions using these drivers to the designated database.

JDBC Vendor

Driver Version

Driver Type

Database Server

Database Version

Apache

10.9.1.0

Embedded or client

Derby

-

Apache

-

-

Cassandra

-

Progress

DataDirect

data connectivity for ODBC and JBDC driver access, data integration, and SaaS and cloud computing solutions

-

-

IBM

JDBC 3.0 version 3.57.82 or JDBC 4.0 version 4.7.85

DB2 Universal JDBC driver

DB2

9.x

IBM

JDBC 3.0 version 3.66.46 or JDBC 4.0 version 4.16.53

DB2 Universal JDBC driver

DB2

10.1

IBM

-

Type IV

Informix

-

Microsoft

4

Type II

MS SQL Server

2012*

Oracle MySQL, MySQL Community

5.x

Type II, Type IV

MySQL

5.x

Open Source

Connector/J 5.1.27

Type IV

MySQL

5.x

Open Source

-

Type IV

Postgres

8.x, 9.x

Oracle

9.x

Type II, Type IV

Oracle Database

8i+

Sybase

jConnect

Type IV

Sybase

-

Teradata
New in 3.9  
  Teradata-

Notes:

  • Type II is a C or OCI driver
  • Type IV is a thin database client and is a pure Java driver

Business Transaction Error Detection

The Java Agent supports the following logging frameworks for business transaction error detection:

  •     Log4j
  •     java.util.logging

If you are using a different logger, see Configuring Error Detection Using Custom Loggers.

NoSQL/Data Grids/Cache Servers Support

These are the known NoSQL, data grids and cache server environments in which the Java Agent has been used to instrument applications. Some require additional configuration. Click the link on the database, data grid or cache name in the following support matrix for information about additional configuration required or related configuration topics. 

Vendor

Database/Data Grid/Cache

Version

Correlation/Entry Points

JMX

Apache

Casandra (DataStax, REST) and Cassandra CQL3

1.x

Correlation

Yes

Apache

Apache Lucene - Apache Solr

1.4.1

Entry Points

Yes

JBoss

JBoss Cache TreeCache

-

-

-

Terracotta

EhCache

-

-

-

Open Source

Memcached

-

-

-

Open Source

MongoDB

-

-

-

Oracle

Coherence

3.7.1

Custom-Exit

Yes

JBoss

Infinispan

5.3.0+

Correlation

-

NoSQL/Data Grids/Cache Servers Configuration

For NoSQL, data grids, and cache server environments that require additional configuration, this section provides some information and links to topics that help you configure the environment.  Environments in the NoSQL/Data Grids/Cache Servers Support table that require additional configuration, link to the configuration table below. 

Database/Data Grid/CacheTopics for Required or Optional Configuration
Apache Cassandra (DataStax, REST) and Cassandra CQL3
Apache Lucene - Apache Solr
JBoss
Terracotta EhCache
Open Source Memcached
Open Source MongoDB
Oracle Coherence

Java Frameworks Support

These are the known Java framework environments in which the Java Agent has been used to instrument applications. Some require additional configuration. Click the link on the Java framework name in the following support matrix for information about additional configuration required or related configuration topics. 

Vendor

Framework

Version

SOA protocol (WebServices)

Auto Naming

Entry Points

Exit Points

Detection

Adobe

BlazeDS

-

HTTP and JMS adaptor

-

Yes

 

-

Adobe

ColdFusion

8.x, 9.x

-

-

Yes

-

Configuration required for transaction discovery

Apache

Cassandra with Thrift framework

-

-

-

Yes

Yes

Apache Thrift Entry and Exit points are detected

Apache

Struts

1.x, 2.x

-

-

Yes

 

Struts Actions are detected as entry points, struts invocation handler is instrumented

Apache

Tapestry

5

-

-

Yes

-

Not by default

 

Wicket

-

-

No

Yes

-

Not by default

Apple

WebObjects

5.4.3

HTTP

Yes

Yes

-

Yes

 

CometD

2.6

HTTP

Yes

Yes

--

Eclipse

RCP (Rich Client Platform)

-

-

-

-

-

-

Google

Google Web Toolkit (GWT)

2.5.1

HTTP

Yes

Yes

-

-

JBoss

JBossWS Native Stack

4.x, 5.x

Native Stack

-

-

-

-

Open Source

Direct Web Remoting (DWR)

-

-

-

-

-

-

Open Source

Enterprise Java Beans (EJB)

2.x, 3.x

-

-

Yes

-

-

Open Source

Grails

-

-

-

Yes

-

Not by default

Open Source

Hibernate JMS Listeners

1.x

-

-

-

-

-

Open Source

Java Abstract Windowing Toolkit (AWT)

-

-

-

-

-

-

Open Source

Java Server Faces (JSF)

1.x

-

Yes

Yes

-

Not by default

Open Source

Java Server Pages

2.x

-

Yes

-

-

Yes

Open Source

Java Servlet API

2.x

-

-

-

-

-

Open SourceJersey1.x, 2.xREST, JAX-RSYesYesNoNot by default
Open SourceWebSocket1.0 (Java EE 7, JSR-356)-

Yes,
BT Naming not configurable 

Yes, correlation
not supported
Yes

Detection is automatic

Open Source - Google

AngularJS

-

-

-

Yes

-

-

Oracle

Coherence with Spring Beans

2.x, 3.x

-

-

-

-

-

Oracle

Swing (GUI)

-

-

-

-

-

-

Oracle

WebCenter

10.0.2,10.3.0

-

-

-

-

-

Open Source

JRuby HTTP

-

-

-

Yes

-

Not by default

Spring

Spring MVC

-

-

-

Yes

-

Not by default

Java Frameworks Configuration

For the Java framework environments that require additional configuration, this section provides some information and links to topics that help you configure the environment.  Environments in the Java Frameworks Support table that require additional configuration, link to the configuration table below. 

Java FrameworkTopics for Required or Optional Configuration
Adobe BlazeDS 
Adobe ColdFusion

Configuration is required for transaction discovery

Apache Cassandra with Thrift framework

No additional configuration is required. See also, 

Apache Struts
Apache Tapestry
Wicket
Apple WebObjects

Business transaction naming can be configured via getter-chains, see

CometD

Open Source Enterprise Java Beans (EJB)

Open Source Hibernate JMS Listeners

No additional configuration is required. See also, 

Open Source Java Server Faces (JSF)
Open Source Java Server Pages

Open Source Jersey

Open Source JRuby HTTP
Open Source WebSocket

Node property: websocket-entry-calls-enabled

Spring MVC

RPC/Web Services API Support

These are the known Java framework environments in which the Java Agent has been used to instrument applications. Some require additional configuration. Click the link on the RPC, web services or API framework name in the following support matrix for information about additional configuration required or related configuration topics.

Vendor

RPC/Web Services API Framework

Version

SOA Protocol-
WebServices

Auto Naming

Correlation/Entry Points

Exit Points

Configurable BT Naming Properties

Detection

Apache

Apache CXF

2.1

JAX-WS

Yes

Yes

Yes

Yes

Yes

Apache

Apache Commons

-

HTTP Client

Yes

Yes

Yes

-

Yes

Apache

Apache Thrift

-

-

Yes

Yes

Yes

Yes

Yes

IBM

WebSphere

6.x

JAX-RPC

-

-

-

-

-

IBM

WebSphere

7.x, 8.x

JAX-RPC

-

-

-

-

-

IBM

Websphere

7.x, 8.x

IIOP

-

-

-

-

-

JBoss

JBoss

4.x, 5.x

RMI

Yes

Yes

Yes

Yes

Yes

Open Source

java.net.Http

-

HTTP

Yes

-

Yes

Yes

Yes

Oracle

GlassFish Metro

-

JAX-WS

-

-

-

-

-

Oracle

GlassFish Metro with Grails

-

JAX-WS

-

Yes

-

-

Not by Default

Oracle

Oracle Application Server

ORMI

-

no

-

-

-

-

Oracle

WebLogic

10.x

T3, IIOP

Yes

Correlation: Yes, Entry: No

Yes

-

Yes

Oracle

WebLogic

9.x, 10.x

JAX-RPC

-

-

-

-

-

Sun

Sun RMI

-

IIOP

-

Not by Default

-

-

-

Sun

Sun RMI

-

JRMP

-

By Default

Yes

host/port

Yes

-

Web Services

-

SOAP over HTTP

-

Yes

Yes

-

-

RPC/Web Services API Framework Configuration

For the RPC and web service API environment that require additional configuration, this section provides some information and links to topics that help you configure the environment.  Environments in the RPC/Web Services API Framework Support table that require additional configuration, link to the configuration table below.