Java Supported Environments

On this page:

Related pages:

Supported Environments and Versions

This topic lists the application environments and versions supported by the AppDynamics Java Agent. Environments or versions that are not listed are not supported. For general information about AppDynamics support, see Supported Environments and Versions.

Supported Platform Matrix for the Java Agent

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 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.
For environments supported by AppDynamics Server Monitoring, Standalone Machine Agent Requirements and Supported Environments.

JVM Support

The AppDynamics Java Agent supports applications running with a JRE or a full JDK. The Java Agent supports the following JVM types and versions.

Vendor	Implementation	Version	Operating System	Object Instance Tracking	Automatic Leak Detection	Custom Memory Structures
						Content Inspection	Access Tracking	Requires JVM Restart?
Azul	Zing	15.x	Linux x64	Yes³	Yes	-	-	-
Azul	Zulu	7.x	Linux x64	Yes³	Yes	-	-	-
Oracle	Java HotSpot	7 Update 45+	Solaris Sparc 64, Windows, Linux	-	-	-	-	-
Oracle	Java SE (Standard Edition)	8¹	Solaris Sparc 64, Windows, Linux	Yes	Yes	Yes	Yes	Yes
BEA	JRockit	1.5	-	-	Yes	Yes	Yes	Yes
BEA	JRockit	1.6, 1.7	-	-	Yes	Yes	-	-
Oracle	JRockit JVM	28.1+	Linux Intel 64 Windows	-	-	-	-	-
IBM	JVM	1.5.x, 1.6.x, 1.7.x	-	-	Yes, as noted²	Yes, as noted²	-	-
SUN	JVM	1.5, 1.6, 1.7	-	Yes	Yes	Yes	Yes	-
Open Source	OpenJDK	1.6, 1.8	Linux, windows, everywhere	Yes	Yes	-	-	-
HP	OpenVMS	-	-	-	-	-	-	-

Notes:

¹For examples of instrumenting new language constructs in Java SE 8, see Instrumenting Java 8 Constructs.

²Object instance tracking, automatic leak detection, and custom memory structure monitoring are not supported with the AppDynamics IBM Java Agent. IBM JVMs can be instrumented with the AppDynamics Sun Java Agent to work around this limitation, however, doing so can result in a noticeable negative performance impact and is not recommended. In such cases, the IBM JVM needs to be restarted to enable custom memory structure monitoring.

³ Object Instance Tracking is supported only for version 4.2.4 and after. In addition, you must also pass the JVM argument (XX:+ProfileLiveObjects) for versions higher than 4.2.4.

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 toolkit (Spray.io)	1.1.x	Yes	Yes	HTTP	Entry points are detected and configurable as servlet entry point and exit points as HTTP exits.
Pivotal	Grails	-	-	-	-

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

Application Servers

The Java Agent supports the following application servers. Some require additional configuration. Click the link on the server or OSGi Runtime for information about additional requirements or related configuration topics. The agent usually discovers application servers 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, 8.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
IBM	WebSphere	8.x	JAX-WS	Yes, detect and correlate	-	Yes
Open Source	Liferay Portal	-	-	-	-	-
Open Source	JBoss Wildfly (formerly JBoss Server)	4.x, 5.x, 6.x, 7.x, 8.x		Yes		Yes
Sun/Oracle	GlassFish Enterprise Server	2.x	-	-	Yes	Yes
Oracle	GlassFish Server and GlassFish Server Open Source Edition	3.x, 4.x	-	-	Yes for AMX	Yes
Oracle and BEA	WebLogic Server	9.x+	JAX-WS	Yes, detect and correlate for 10.x	Yes	Yes
Red Hat	JBoss Enterprise Application Server	6.11, 6.2.0, 7.x		Yes		Yes
Software AG	webMethods	9.5, 9.6	-	-	-	Yes
Tibco	ActiveMatrix BusinessWorks Service Engine	5.x	-	-	-	Yes
	Application Server (OC4J)	-	-	Yes, detect and correlate for 10.x	-	Yes
-	Grails, with Tomcat 7.x, Glassfish v3, Weblogic 12.1.1 (12c)	-	-	-	-

Notes:

Servlet 3.x detection is not supported.

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 Server	Configuration Notes
Apache Felix	OSGi Infrastructure Configuration
Apache Sling	OSGi Infrastructure Configuration
Apache Tomcat	Apache Tomcat Startup Settings
Apache Resin	Resin Startup Settings
Apache Cold Fusion	Requires configuration for transaction discovery; see Servlet Entry Points
Equinox	OSGi Infrastructure Configuration
Eclipse Jetty	Jetty Startup Settings
IBM InfoSphere	IBM WebSphere and InfoSphere Startup Settings
IBM WebSphere	IBM WebSphere and InfoSphere Startup Settings
Sun GlassFish Enterprise Server	Manually configure GlassFish JDBC connection pools using MBean attributes and custom JMX metrics GlassFish Startup Settings Modify GlassFish JVM Options
Oracle GlassFish Server (including GlassFish Server Open Source Edition)	GlassFish Startup Settings Modify GlassFish JVM Options
Oracle and BEA WebLogic Server	Oracle WebLogic Startup Settings
Software AG webMethods	webMethods Startup Settings
Tibco ActiveMatrix BusinessWorks Service Engine	Tibco ActiveMatrix BusinessWorks Service Engine Settings
Open source JBoss Wildfly	JBoss and Wildfly Startup Settings
Red Hat JBoss Enterprise Application Server	JBoss and Wildfly Startup Settings
Red Hat JBoss Web Server	JBoss and Wildfly Startup Settings

PaaS Providers

PaaS Provider	Buildpack
Pivotal Cloud Foundry	Java Buildpack 3.4 and higher. (See Using AppDynamics with Java Applications on Pivotal Cloud for a walkthrough of using the Java buildpack.)
Red Hat Openshift 3	JBoss EAP 6.4 and WildFly 8.1 Docker images. For documentation and download information, see the AppDynamics Java APM Agent page on the Red Hat Customer Portal.

Message Oriented Middleware Support

The Java Agent supports the following message oriented middleware environments. 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	Configuration Notes
Amazon	Simple Queue Service (SQS)	-	-	Yes (correlation only)	Yes	-	See "Amazon Simple Queue Service Backends" on Java Backend Detection
Amazon	Simple Notification Service (SNS)	-	-	No	Yes	-	See "Amazon Simple Notification Service Backends" on Java Backend Detection
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	Example Message Queue Backend Configuration
Apache	Axis	1.x, 2.x	JAX-WS	Yes	Yes	-	Default exclude rules exist for Apache Axis, Axis2, and Axis Admin Servlets. See aslo "Web Service Entry Points" on Java Backend Detection.
Apache	Apache CXF	2.1	JAX-WS	Yes	Yes	-	To enable correlation, set node property enable-soap-header-correlation=true.
Apache	Synapse	2.1	HTTP	Yes	Yes	-	To enable correlation, set node property enable-soap-header-correlation=true.
Fiorano	Fiorano MQ		-	-	-	-
IBM	IBM Web Application Server (WAS)	6.1+, 7.x	Embedded JMS	-	Yes	-	Example Message Queue Backend Configuration
IBM	IBM MQ (formerly IBM WebSphere MQ)	6.x+	JMS	Yes	Yes	-	Example Message Queue Backend Configuration
Open Source	Open MQ	-	-	-	-	-
Mulesoft	Mule ESB	3.4	HTTP	Yes	Yes	-	Mule ESB Startup Settings Mule ESB Support
Oracle	Java Message Service	2.0	JMS	Correlation of the listener is disabled by default	Yes
Oracle	Oracle AQ	-	JMS	-	Yes	-
Oracle / BEA	WebLogic	9.x+	JMS 1.1	Yes	Yes	Yes	Oracle WebLogic Startup Settings
Progress	SonicMQ	-	-	-	-	-
Pivotal	RabbitMQ	-	HTTP	-	Yes	-	See "RabbitMQ Backends" on Java Backend Detection
Rabbit	RabbitMQ Spring Client	-	-	Yes	Yes	-	See "RabbitMQ Backends" on Java Backend Detection
Red Hat	HornetQ (formerly JBoss Messaging and JBoss MQ)	-				Yes
Red Hat	JBoss A-MQ	4.x+	-	-	-	Yes
Spring	Spring Integration	2.2.0	JMS	Yes	Yes	Yes	Spring Integration Support See also "Java Message Service Backends" on Java Backend Detection
WSO2	ESB	4.7.0	-	Yes	Yes	-

JDBC Drivers and Database Servers Support

The Java Agent supports the following JDBC drivers and database server environments. 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			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:

Apache Log4j and Log4j 2
java.util.logging
Simple Logging Facade for Java (SLF4J)
Support for the following method has been added: public void error(String format, Object.... argArray)
Logback

To instrument other types of loggers, see Configure Error Detection.

NoSQL/Data Grids/Cache Servers Support

The Java Agent supports these NoSQL, data grids and cache server environments. 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	Configuration Notes
Amazon	DynamoDB	-	Exit Points	-	See "Amazon Web Services" on Java Backend Detection.
Amazon	Simple Storage Service (S3)	-	-	-	"Amazon Simple Storage Service Backends" on Java Backend Detection.
Apache	Casandra DataStax drivers Thrift drivers	1.x, 2.x	Correlation for Thrift drivers only	Yes	"Cassandra Backends" on Java Backend Detection. For Cassandra server-side support, see Apache Cassandra Startup Settings
Apache	Lucene - Apache Solr	1.4.1	Entry Points	Yes	Solr Startup Settings
JBoss	Cache TreeCache	-	-	-	JBoss Startup Settings
JBoss	Infinispan	5.3.0+	Correlation	-	-
Red Hat	JBoss DataGrid	-	-	-	JBoss Startup Settings
	JBoss Cache TreeCache	-	-	-
	JBoss Infinispan	5.3.0+	Correlation	-
Terracotta	EhCache	-	-	-	EhCache Exit Points
Open Source	Memcached	-	-	-	Memcached Exit Points
Open Source	MongoDB	3.1	-	-	See "MongoDB Backends" on Java Backend Detection
Oracle	Coherence	3.7.1	Custom-Exit	Yes	Coherence Startup Settings

Java Frameworks Support

The Java Agent supports these Java frameworks. 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, 2.x	-	Yes	Yes	-	-
Open Source	Java Server Pages	2.x	-	Yes	-	-	Yes
Open Source	Java Servlet API	2.x	-	-	-	-	-
Open Source	Jersey	1.x, 2.x	REST, JAX-RS	Yes	Yes	No	Not by default
Open Source	WebSocket	1.0 (Java EE 7, JSR-356)	-	Yes, BT Naming not configurable	Yes, correlation not supported	Yes	Detection is automatic
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 Framework	Configuration Notes
Adobe BlazeDS	Example Message Queue Backend Configuration
Adobe ColdFusion	Configuration is required for transaction discovery Java Business Transaction Detection Servlet Entry Points
Apache Cassandra with Thrift framework	No additional configuration is required.
Apache Struts	Struts Entry Points
Apache Tapestry	Java Business Transaction Detection Servlet Entry Points
Wicket	Java Business Transaction Detection Servlet Entry Points
Apple WebObjects	Business transaction naming can be configured via getter-chains, see Getter Chains in Java Configurations Detect Transactions by POJO Method Invoked by a Servlet
CometD	See also "HTTP Exit Points" on Java Backend Detection.
Open Source Enterprise Java Beans (EJB)	EJB Entry Points
Open Source Hibernate JMS Listeners	No additional configuration is required. See also: Advanced Options in Call Graphs
Open Source Java Server Faces (JSF)	Java Business Transaction Detection and Servlet Entry Points
Open Source Java Server Pages	Servlet Entry Points
Open Source Jersey	JAX-RS Support and node properties: rest-num-segments rest-transaction rest-uri-segment-scheme See App Agent Node Properties Reference for information on the properties.
Open Source JRuby HTTP	Java Business Transaction Detection Servlet Entry Points
Open Source WebSocket	Node property: websocket-entry-calls-enabled
Spring MVC	Java Business Transaction Detection Servlet Entry Points

RPC/Web Services API/HTTP Client Support

The Java Agent supports these RPC, web service, and API framework types.

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 HTTP Client	-	HTTPClient (now in Apache HTTP Components)	Yes	Yes (correlation only)	Yes	-	Yes
Apache	Netflix-ribbon HTTP Client	2.1.0	HTTP Client	Yes	Yes (correlation) Entry - NA	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	-	-	-	-	-
Red Hat	JBoss A-MQ	4.x+	RMI	Yes	Yes	Yes	Yes	Yes
Open Source	java.net.Http	-	HTTP	Yes	-	Yes	Yes	Yes
Open Source	HTTPClient	0.3-3	Oracle SOA (and potentially others that embed this library)	-	Correlation: Yes; Entry: No	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	-	-	-	-	-
Square	OkHttp
Square	OkHttp	-	HTTP	Yes	Correlation: Yes Entry: No	Yes	-	Synchronous only
Sun	Sun RMI	-	IIOP	-	Not by Default	-	-	-
Sun	Sun RMI	-	JRMP	-	No	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.

RPC/Web Services API	Configuration Notes
Apache Commons	See "HTTP Backends" on Java Backend Detection.
Apache Thrift	Binary Remoting Entry Points for Apache Thrift
IBM WebSphere	IBM WebSphere and InfoSphere Startup Settings Instrument JVMs in a Dynamic Environment. See also Default configuration excludes WebSphere classes.
JBoss	JBoss and Wildfly Startup Settings
Open Source java.net.Http	See HTTP Exit Points on Java Backend Detection.
Oracle WebLogic	Oracle WebLogic Startup Settings Default configuration excludes WebLogic classes
Web Services	Create Match Rules for Web Services "Web Service Entry Points" on Java Backend Detection