Download PDF
Download page Java Supported Environments.
Java Supported Environments
This page lists the application environments and versions supported by the AppDynamics Java Agent.
Java Agent Supported Platforms
In the following tables, note that:
- 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 Visibility, Machine Agent Requirements and Supported Environments.
JVM Support
The AppDynamics Java Agent uses the standard JVM Tool Interface (JVMTI) mechanism allowing it to instrument any software running on a JVM supporting this mechanism.
AppDynamics certifies the successful operation of the basic mechanisms of instrumentation used by the agent on the following Java runtimes. These capabilities are supported on both JRE or full JDK installations.
Where the agent supports the following advanced memory monitoring features, they are listed for the JVM: Object Instance Tracking (OIT), Automatic Leak Detection (ALD), Content Inspection (CI), and Access Tracking (AT).
Unless listed on this page, builds downloaded from other sources are not officially supported.
| JVM | OS | Memory Monitoring Features |
|---|---|---|
| AdoptOpenJDK 8, 9, 10, 11, 12, 13, 14, 15, 16 ( supported for both Hotspot and OpenJ9 JVMs) | Linux, Windows, MacOS | OIT (supported only for Hotspot JVM), ALD, CI, AT |
| Amazon Corretto 8, 11, and 17 | Linux, Windows | OIT, ALD, CI, AT |
| Azul Zing 15.x. | Linux x64 | OIT, ALD |
Azul Zulu OpenJDK 1.6, 1.7, 1.8, 9, 10, 11, 13, 14, 15, 16, 17 JDK11 is supported from 4.5.6 onwards JDK13 is supported from 4.5.15 onwards JDK14 is supported from 20.4.0 onwards JDK15 is supported from 20.10.0 onwards JDK16 is supported from 21.4.0 onwards JDK17 is supported from 21.11.0 onwards | Linux, Windows | OIT, ALD, CI, AT |
| JVM - BellSoft Liberica JDK 8, 11, 16, and 17 | Linux, Windows, MacOS | OIT, ALD |
| GraalVM 20.0.0, 20.2.0, 21.1.0, 21.3.0 | Linux, Windows, MacOS | OIT, ALD, CI, AT |
| HP OpenVMS | ||
| IBM JVM 1.6.x, 1.7.x, 1.8.x | AIX, HP-UX, Linux, Solaris, Windows, z/OS | ALD, CI 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, this only enables automatic leak detection and custom memory structure monitoring. Object instance tracking is not available. Working around this limitation can result in negative performance impact and is not recommended. In such cases, the IBM JVM needs to be restarted to enable custom memory structure monitoring. |
| Oracle Rockit JVM 28.1+ | Linux Intel 64, Windows | |
| Oracle/BEA JRockit 1.6 | ||
Oracle/Sun JVM 1.6, 1.7, 1.8, 9, 10, 11, 12, 13, 14, 15, 16, 17 JDK11 is supported from 4.5.6 onwards JDK12 is supported from 4.5.11 onwards JDK13 is supported from 4.5.15 onwards JDK14 is supported from 20.4.0 onwards JDK15 is supported from 20.10.0 onwards JDK16 is supported from 21.4.0 onwards JDK17 is supported from 21.11.0 onwards | Solaris Sparc 64, Windows, Linux | OIT, ALD, CI, AT Content Inspection and Access Tracking require a JVM restart. |
Oracle OpenJDK 1.7, 1.8, 9, 10, 11, 12, 13, 14, 15, 16, 17
Oracle OpenJDK builds supported above are those that can be downloaded from https://jdk.java.net/. OpenJDK11 is supported from 4.5.6 onwards JDK13 is supported from 4.5.15 onwards JDK14 is supported from 20.4.0 onwards JDK15 is supported from 20.10.0 onwards JDK16 is supported from 21.4.0 onwards JDK17 is supported from 21.11.0 onwards | Solaris Sparc 64, Windows, Linux | OIT, ALD |
| SAP JDK 6+ | Windows, Solaris, Linux, HP-UX, i5/OS, AIX |
JVM Application Server and Framework Support
AppDynamics supports the use of the Java Agent to instrument any application component running on a supported JVM, irrespective of how that component is built. The power of the AppDynamics platform is that it can automatically discover the topology and behavior of complex enterprise applications without requiring deep technical knowledge of the application's underlying code.
Frequently, Java-based systems employ standard framework code to implement business logic. Automatic instrumentation of framework code relies on knowledge of the business logic and programming patterns employed by the framework. AppDynamics instrumentation targets processing hand-offs between components, called entry points and exit points, either within the JVM or between JVMs. This includes hand-offs between frameworks in cases where multiple frameworks are being used together. This section covers the capabilities for frameworks for which AppDynamics provides automatic detection rules.
Monitoring application components built using frameworks not listed here may require custom configuration. The custom configuration may involve, for example, custom POJO entry or exit points. If you understand how the application behaves internally, you can easily configure this type of instrumentation. For more complex configuration tasks, contact your account representative to discuss how to engage the AppDynamics customer success organization.
JVM Language Frameworks Support
No additional configuration is required for these frameworks.
Vendor | JVM Language | Version | Correlation/ | Exit Points | Transports | Notes |
|---|---|---|---|---|---|---|
Open Source | Akka Actor | 2.1 – 2.5.x | Yes | Yes | Netty | 4.3.1 required for 2.4.x 2.5x support includes Persistence Remoting exit/entry supported |
Open Source | Akka HTTP Name: Type: Boolean Default: False | Akka Actor 2.5.x Akka HTTP upto 10.2.6 Scala 2.11, 2.12 | Yes | Yes | HTTP | EUM is supported Support for Non-Route DSL |
| Open Source | Http4s Blaze Client | Blaze versions: 0.21.1, 0.21.0, 0.20.23, 0.20.5 | No | Yes | HTTP | |
Open Source | Groovy | - | Yes | Yes | ||
| Open Source | Ktor | 1.0.x -1.6.x | Yes (Netty Engine) | - | HTTP | EUM is supported |
Open Source | Play for Scala Play for Java | 2.1 – 2.8 Scala 2.11, 2.12 | Yes | - | HTTP over Netty server Akka HTTP server | Includes framework specific entry and exit points Play EUM-APM correlation supported |
Open Source | Scala | 2.11.6 | ||||
| Open Source | Spray toolkit (Spray.io) | 1.1.x 1.1.3 | Yes | Yes | HTTP | Entry points are detected and configurable as servlet entry point and exit points as HTTP exits |
Pivotal | Grails | - | - | - | - |
Java Frameworks Support
The Java Agent supports these Java frameworks. Some require additional configuration as indicated in the Configuration Notes column.
Vendor | Framework | Version | SOA protocol (WebServices) | Auto Naming | Entry Points | Exit Points | Detection | Configuration Notes |
|---|---|---|---|---|---|---|---|---|
Adobe | BlazeDS | - | HTTP and JMS adaptor | - | Yes | - | Example Message Queue Backend Configuration | |
Adobe | ColdFusion | 8.x, 9.x | - | - | Yes | - | Configuration required for transaction discovery | Configuration is required for transaction discovery. See: |
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 | Struts Entry Points | |
Apache | Tapestry | 5 | - | - | Yes | - | Not by default | See: |
| Apache | Wicket | - | - | No | Yes | - | Not by default | See: |
| Apple | WebObjects | 5.4.3 | HTTP | Yes | Yes | - | Yes | |
| axonframework.org | Axon | 2.x, 3.x | - | - | Commands on the Command Bus continue existing Business Transactions | Correlation for Distributed Command Bus on JGroups and for Spring Cloud Connector transport as an exit | ||
Open Source | CometD | 2.6 | HTTP | Yes | Yes | - | - | See also "HTTP Exit Points" on Java Backend Detection. |
| Open Source | Spring Batch | - | Spring Batch Support | |||||
Eclipse | RCP (Rich Client Platform) | - | - | - | - | - | - | |
Google Web Toolkit (GWT) | 2.5.1 | HTTP | Yes | Yes | - | - | ||
JBoss | JBossWS Native Stack | 4.x, 5.x | Native Stack | - | - | - | - | |
| IBM | IBM-BPM | 8.5.7, 8.6 | - | Yes | Yes | Yes | Yes | IBM-BPM Support |
Open Source | Direct Web Remoting (DWR) | - | - | - | - | - | - | |
| Open Source | Eclipse Vert.x Core | 3.3.3-3.5.4, 3.6.x, 3.7.x, 3.8.x, 3.9.x, 4.0.x, 4.1.x, 4.2.x | HTTP | Yes | Yes | Yes | Yes | EUM Correlation is supported |
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 | - | - | Java Business Transaction Detection and Servlet Entry Points |
Open Source | Java Server Pages | 2.x | - | Yes | - | - | Yes | |
Open Source | Java Servlet API | 2.x, 3.0 | - | - | - | - | - | |
| Open Source | Jersey | 1.x, 2.x | REST, JAX-RS | Yes | Yes | No | Not by default | JAX-RS Support and node properties:
See App Agent Node Properties Reference for information on the properties. |
Open Source | JRuby HTTP | - | - | - | Yes | - | Not by default | See: |
| Open Source | Micronaut | 1.1.0 to 3.1.4 | - | Yes | Yes | Yes | By default | - |
| Open Source | Netty | 3.x, 4.x | HTTP | Yes | Yes | Yes | By default |
|
| Open Source | Spring Annotated Web Services | 2.x+ | HTTP | Yes | Yes | No | - | |
| Open Source | Spring WebFlux | 5.0, 5.1, 5.2, 5.3 | HTTP | Yes | Spring Boot (Netty, Jetty, Tomcat, Undertow) | WebClient (Reactor Netty, Reactive Jetty) | By default | The node property This node property should not be enabled unless there is some issue or loss in visibility with the OOTB support. By default, the value of this property is false. |
| Open Source | Spring Cloud Gateway | 2.0.x, 2.1.x, 2.2.x, 3.0.x | HTTP | Yes | Yes | Yes | By default | |
| Open Source | WebSocket | 1.0 (Java EE 7, JSR-356) | - | Yes, | Yes, correlation not supported | Yes | Detection is automatic | Node property: websocket-entry-calls-enabled |
Oracle | Coherence with Spring Beans | 2.x, 3.x | - | - | - | - | - | |
Oracle | Swing (GUI) | - | - | - | - | - | - | |
Oracle | WebCenter | 10.0.2,10.3.0 | - | - | - | - | - | |
Spring | Spring MVC | 5.3 | - | - | Yes | - | Not by default |
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 / | Version | SOA Protocol | RMI Supported | JMX | Entry Points | Configuration Notes |
|---|---|---|---|---|---|---|---|
Adobe | Cold Fusion | 8.x, 9.x | - | No | - | Yes | Requires configuration for transaction discovery; see Servlet Entry Points |
Equinox | - | - | - | - | Yes | ||
Apache | Felix | - | - | - | - | Yes | |
Apache | Sling | - | - | - | - | Yes | |
Apache | Tomcat | 5.x, 6.x, 7.x, 8.x, 9, 10 | - | - | Yes | Yes | Apache Tomcat Startup Settings |
Apache | Resin | 1.x - 4.x | - | - | - | - | |
Eclipse | Jetty | 6.x, 7.x, 8x, 9x | - | - | - | - | Jetty Startup Settings |
| IBM | InfoSphere | 8.x | - | - | - | Yes | IBM WebSphere and InfoSphere Startup Settings |
IBM | WebSphere | 6.1, 7.x, 8.x, 9.x | JAX-WS | Yes, detect and correlate | Yes for WebSphere PMI | Yes | IBM WebSphere and InfoSphere Startup Settings |
Open Source | Liferay Portal | - | - | - | - | - | |
| Open Source | JBoss EAP | 7.1.5, 7.2.0, 7.3.0 | Yes | Yes | JBoss and Wildfly Startup Settings | ||
| Open Source | JBoss Wildfly (formerly JBoss Application Server) | 4.x to 25.x | Yes | Yes | JBoss and Wildfly Startup Settings | ||
| Sun/Oracle | GlassFish Enterprise Server | 2.x | - | - | Yes | Yes | GlassFish Startup Settings |
Oracle | GlassFish Server and | 3.x, 4.x | - | - | Yes for AMX | Yes | GlassFish Startup Settings |
Oracle and BEA | WebLogic Server | 9.x+ | JAX-WS | Yes, detect and correlate for 10.x To enable correlation using a header transported in the | Yes | Yes | Oracle WebLogic Startup Settings |
| Software AG | webMethods | 9.5, 9.6, 10.x | - | - | - | Yes | |
| Tibco | ActiveMatrix BusinessWorks Service Engine | 5.x, 6.x | - | To enable correlation using a header transported in the | - | Yes | |
Application Server (OC4J) | - | - | Yes, detect and correlate for 10.x | - | Yes | ||
- | Grails, with Tomcat 7.x, Glassfish v3, Weblogic 12.1.1 (12c) | - | - | - | - |
Servlet 3.x detection is not supported.
PaaS Providers
| PaaS Provider | Buildpack |
|---|---|
| Pivotal Cloud Foundry | See Using AppDynamics with Java Applications on Pivotal Cloud for more information. |
| Red Hat Openshift 3 | JBoss EAP 6.4 and 7.x 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 as indicated in the Configuration Notes column. 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 | |
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 | Kafka | 0.9.0.0 to 2.8.1 | - | Yes | Yes | Yes | Kafka consumer entry points are disabled by default. Correlation is supported. See Apache Kafka Consumer Backends. |
Apache | Synapse | 2.1 | HTTP | Yes | Yes | - | To enable correlation, set node property |
Fiorano | Fiorano MQ | - | - | - | - | ||
IBM | IBM Web Application Server (WAS) | 6.1+, 7.x | Embedded JMS | - | Yes | - | |
IBM | IBM MQ (formerly IBM WebSphere MQ) | 6+ | JMS | Yes | Yes | - | |
Mulesoft | Mule ESB | 3.4, 3.6, 3.7, 3.8, 3.9, 4.1.x, 4.2.0, 4.2.1, 4.2.x, 4.3.0 | HTTP, JMS | Yes | Yes | - | |
| Open Source | Eclipse Vert.x verticles | 3.3.x, 3.4.x, 3.5.0, 3.6.0 | - | Yes (correlation only) | Yes | - | The Java Agent detects messaging exit calls between verticles. |
Open Source | Open MQ | - | - | - | - | - | |
| Oracle | Java Message Service | 2.0 | JMS | Correlation of the listener is disabled by default | Yes | ||
Oracle | Oracle AQ | - | JMS | - | Yes | - | |
| Oracle | OSB deployed on WebLogic | 12.2.1 | HTTP JMS | Yes | Yes | ||
Oracle / BEA | WebLogic | 9.x+ | JMS 1.1 | Yes | Yes | Yes | |
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+, 4.0+ | JMS | Yes | Yes | Yes | See also "Java Message Service Backends" on Java Backend Detection |
| WSO2 | ESB | 4.7.0 | - | Yes | Yes | - | EUM Correlation is not supported |
| WSO2 | API Microgateway | 3.1.x, 3.2.0, 3.2.3 | HTTP1 | Yes | Yes | - | See WSO2 API Microgateway Startup Settings |
JDBC Drivers and Database Servers Support
The Java Agent supports these JDBC driver 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 | - | DB2 Universal JDBC driver | DB2 | 11.x |
IBM | - | Type IV | Informix | - |
| Maria | 1.4.x - 2.6.x | |||
Microsoft | 4 | Type II | MS SQL Server | 2012 |
Oracle MySQL, MySQL Community | 5.x, 6.x, 8.x | Type II, Type IV | MySQL | 5.x |
| Oracle | RAC | |||
Oracle | 9i, 10g 11g, 12c, 18c, 19c | Type II, Type IV | Oracle Database | 8i+ |
Open Source PostgreSQL | 42.2.5 | Type IV | Postgres | 8.x, 9.x, 11x |
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
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
| 1.x, 2.x | Correlation for Thrift drivers only | Yes |
|
Apache | Lucene - Apache Solr | 1.4.1 | Entry Points | Yes | |
Couchbase | Couchbase | 3.x | Exit Points | - | See "Couchbase Backends" on Java Backend Detection |
JBoss | Cache TreeCache | - | - | - | |
| JBoss | Infinispan | 5.3.0+ | Correlation | - | - |
Open Source | Memcached | - | - | - | |
| Open Source | MongoDB Async Driver | 3.4-3.12 | - | - | See "MongoDB Backends" on Java Backend Detection |
Open Source | MongoDB Sync Driver | 3.1-3.12, 4.0.x | - | - | See "MongoDB Backends" on Java Backend Detection |
| Open Source | MongoDB Reactive Streams Driver | 1.3-1.13, 4.0.x | - | - | See "MongoDB Backends" on Java Backend Detection |
Oracle | Coherence | 3.7.1 | Custom-Exit | Yes | |
| Red Hat | JBoss DataGrid | - | - | - | |
| JBoss Cache TreeCache | - | - | - | ||
| JBoss Infinispan | 5.3.0+ | Correlation | - | ||
Terracotta | EhCache | - | - | - |
RPC/Web Services API/HTTP Client Support
The Java Agent supports these RPC, web services or API framework types. Some require additional configuration as indicated in the Configuration Notes column.
Vendor | RPC/Web Services API Framework/HTTP Client Support | Version | SOA Protocol- | Auto Naming | Correlation/Entry Points | Exit Points | Configurable BT Naming Properties | Detection | Configuration Notes |
|---|---|---|---|---|---|---|---|---|---|
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 | See "HTTP Backends" on Java Backend Detection |
| Apache | Apache Async HTTP Client | 4.1.x | - | - | - | - | - | - | - |
| Apache | Ribbon HTTP Client | 2.7.18 | HTTP Client | Yes | Yes (correlation) Entry - NA | Yes | NA | Yes | |
Apache | Apache Thrift | - | - | Yes | Yes | Yes | Yes | Yes | Binary Remoting Entry Points for Apache Thrift |
| Eclipse | Jetty | 8.x, 9.x | HTTP Client | Yes | Yes (correlation only) | Yes (ART supported) | - | Yes | See "HTTP Backends" on Java Backend Detection |
| gRPC | 1.6.x to 1.42.x | RPC | Yes | Yes (Asynchronous) | Yes (Asynchronous) | ServiceName/MethodName | Yes | See Web Service Backend | |
IBM | WebSphere | 6.x, 7.x, 8.x | JAX-RPC | - | - | - | - | - | IBM WebSphere and InfoSphere Startup Settings; also see Default configuration excludes WebSphere classes |
IBM | Websphere | 7.x, 8.x | IIOP | - | - | - | - | - | IBM WebSphere and InfoSphere Startup Settings; also see Default configuration excludes WebSphere classes |
| IBM | Websphere | 6.1, 7.x, 8.x, 9.x | JAX-WS | Yes | Yes, detect and correlate. To enable correlation using a header transported in the | - | Web Service naming | Yes | - |
| JBoss | 7,8,11,16, and 18 | JAX-WS | Yes | Yes, detect and correlate. To enable correlation using a header transported in the SOAP:Envelope set node property enable-soap-header-correlation=true | Web Service naming | Yes | To detect Web Service entry and to support correlation you must create a Servlet exclude rule. See Web Service Entry Points to exclude a rule for JBoss. | ||
Open Source |
| - | HTTP | Yes | - | Yes | Yes | Yes | See "HTTP Backends" on Java Backend Detection. |
| Open Source | HTTPClient | 0.3-3 | Oracle SOA (and potentially others that embed this library) | - | Correlation: Yes; Entry: No | Yes | - | Yes | Oracle WebLogic Startup Settings; also see Default configuration excludes WebLogic classes |
| Open Source | Grizzly | Grizzly Async HTTP Client (c
| HTTP | - | Correlation: Yes; Entry:No | Yes | - | Yes | |
Oracle | GlassFish Metro | - | JAX-WS | - | - | - | - | - | |
| Oracle | GlassFish Metro with Grails | - | JAX-WS | - | Yes | - | - | Not by Default | |
| Oracle | JAX-WS RI | 2.3.1 | JAX-WS | - | To enable correlation using a header transported in the SOAP:Envelope set node property enable-soap-header-correlation=true | - | Web Service naming | Yes | - |
| Spring WS | Web Services | 3.x, 4.x, and 5.x | HTTP, SOAP | - | To enable correlation using a header transported in the SOAP:Envelope set node property enable-soap-header-correlation=true | - | Web Service naming | Yes | - |
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 | - | - | - | - | - | |
Oracle/Sun | Java | 11 | - | - | - | Yes (ART supported) | - | Yes | |
Oracle/Sun | Sun RMI | - | IIOP | - | Not by Default | - | - | - | |
Oracle/Sun | Sun RMI | - | JRMP | - | No | Yes | host/port | Yes | |
Red Hat | JBoss A-MQ | 4.x+ | RMI | Yes | Yes | Yes | Yes | Yes | JBoss and Wildfly Startup Settings |
| Square | OkHttp | 2.x, 3.x, 4.x (upto 4.9.3) | HTTP | Yes | Correlation: Yes Entry: No | Yes | - | Synchronous (2.x, 3.x, and 4.x upto 4.9.1) and Asynchronous (3.x and 4.x upto 4.9.1) | |
- | Web Services | - | SOAP over HTTP | - | Yes | Yes | - | - | Create Match Rules for Web Services "Web Service Entry Points" on Java Backend Detection |
| jersey.github.io | Reactive JAX-RS client API | 2.25+ | HTTP Client | Yes | Yes (correlation) Entry – NA | Yes | NA | Yes | "Web Service Entry Points" on Java Backend Detection |
Business Transaction Error Detection
The Java Agent supports the following logging frameworks for business transaction error detection:
- Apache
Log4jandLog4j 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 Error Detection.