AppDynamics switched from Semantic Versioning to Calendar Versioning starting in February 2020 for some agents and March 2020 for the entire product suite.


    Skip to end of metadata
    Go to start of metadata

    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).

    JVMOSMemory Monitoring Features
    AdoptOpenJDK 8, 9, 10, 11, 12, 13, 14 ( supported for both Hotspot and OpenJ9 JVMs)Linux, Windows, MacOSALD
    Amazon Corretto 8, 11Linux, Windows
    Azul Zing 15.x.Linux x64OIT, ALD

    Azul Zulu OpenJDK 1.6, 1.7, 1.8, 9, 10, 11, 13

    JDK11 is supported from 4.5.6 onwards

    JDK13 is supported from 4.5.15 onwards

    JDK14 is supported from 20.4.0 onwards

    Linux, Windows

    OIT, ALD, CI, AT


    HP OpenVMS

    IBM JVM 1.6.x, 1.7.x, 1.8.x

    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

    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

    Solaris Sparc 64, Windows, Linux

    OIT, ALD, CI, AT

    Content Inspection and Access Tracking require a JVM restart.

    Open Source OpenJDK  1.7, 1.8, 9, 10, 11, 12, 13

    OpenJDK11 is supported from 4.5.6 onwards
    OpenJDK12 is supported from 4.5.11 onwards

    JDK13 is supported from 4.5.15 onwards

    JDK14 is supported from 20.4.0 onwards

    Solaris Sparc 64, Windows, LinuxOIT, 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 
    Framework

    Version

    Correlation/
    Entry Points

    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: akka-http-stream-entry-enabled

    Type: Boolean

    Default: False

    Akka Actor 2.5.x

    Akka HTTP upto 10.1.5

    Scala 2.11, 2.12

    Yes

    Yes

    HTTP

    EUM is supported

    Support for Non-Route DSL

    Open Source

    Groovy

    -

    Yes

    Yes



    Open Source

    Play for Scala

    Play for Java

    2.1 – 2.6

    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

    Scala2.11.6



    Open SourceSpray toolkit (Spray.io)

    1.1.x

    1.1.3

    YesYesHTTPEntry 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

    Apple WebObjects Startup Settings

    axonframework.orgAxon2.x, 3.x--Commands on the Command Bus continue existing Business TransactionsCorrelation 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 SourceSpring Batch-




    Spring Batch Support

    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

    -

    -

    -

    -


    IBMIBM-BPM8.5.7, 8.6-YesYesYesYesIBM-BPM Support

    Open Source

    Direct Web Remoting (DWR)

    -

    -

    -

    -

    -

    -


    Open Source

    Eclipse Vert.x Core

    3.3.3-3.5.4, 3.6.x, 3.8.x

    HTTP

    Yes

    Yes 

    Yes

    Yes

    EUM Correlation is supported

    Open Source

    Enterprise Java Beans (EJB)

    2.x, 3.x

    -

    -

    Yes

    -

    -

    EJB Entry Points

    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

    Servlet Entry Points

    Open Source

    Java Servlet API

    2.x, 3.0

    -

    -

    -

    -

    -


    Open SourceJersey1.x, 2.xREST, JAX-RSYesYesNoNot by default

    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

    -

    -

    -

    Yes

    -

    Not by default

    See:

    Open SourceMicronaut1.1.0-YesYesYesBy default-
    Open SourceNetty3.x, 4.xHTTPYesYesYesBy default
    • Node property to disable Netty Instrumentation: netty-enabled, by default it is true
    Open SourceSpring Annotated Web Services2.x+HTTPYesYesNo-
    Open SourceSpring WebFlux5.0, 5.1, 5.2HTTPYesSpring Boot (Netty, Jetty, Tomcat, Undertow)WebClient (Reactor Netty, Reactive Jetty)By default-
    Open SourceWebSocket1.0 (Java EE 7, JSR-356)-

    Yes,
    BT Naming not configurable 

    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

    -

    -

    -

    Yes

    -

    Not by default

    See App Agent Node Properties Reference.

    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

    Configuration Notes

    Adobe

    Cold Fusion

    8.x, 9.x

    -

    No

    -

    Yes

    Requires configuration for transaction discovery; see Servlet Entry Points


    Equinox

    -

    -

    -

    -

    Yes

    OSGi Infrastructure Configuration

    Apache

    Felix

    -

    -

    -

    -

    Yes

    OSGi Infrastructure Configuration

    Apache

    Sling

    -

    -

    -

    -

    Yes

    OSGi Infrastructure Configuration

    Apache

    Tomcat

    5.x, 6.x, 7.x, 8.x, 9

    -

    -

    Yes


    Apache Tomcat Startup Settings

    Apache

    Resin

    1.x - 4.x

    -

    -

    -

    -

    Resin Startup Settings

    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 Wildfly (formerly JBoss Application Server)

    4.x to 17.x
    Yes
    YesJBoss and Wildfly Startup Settings
    Sun/Oracle

    GlassFish Enterprise Server

    2.x

    -

    -

    Yes

    Yes

    GlassFish Startup Settings

    Oracle

    GlassFish Server and 
    GlassFish Server Open Source Edition

    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 SOAP:Envelope set node property enable-soap-header-correlation=true

    Yes

    Yes

    Oracle WebLogic Startup Settings
    Software AGwebMethods9.5, 9.6---Yes

    webMethods Startup Settings

    TibcoActiveMatrix BusinessWorks Service Engine5.x, 6.x-

    To enable correlation using a header transported in the SOAP:Envelope set node property enable-soap-header-correlation=true

    -Yes

    Tibco ActiveMatrix BusinessWorks Service Engine Settings


    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 ProviderBuildpack
    Pivotal Cloud Foundry

    Java Buildpack 3.4 and higher 

    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
    AmazonSimple Queue Service (SQS)--Yes (correlation only)Yes-

    See "Amazon Simple Queue Service Backends" on Java Backend Detection

    AmazonSimple Notification Service (SNS)--NoYes

    -

    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.
    ApacheKafka

    0.9.0.0 to 2.0.0

    -YesYesYesKafka 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 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+

    JMS

    Yes

    Yes

    -

    Example Message Queue Backend Configuration

    Mulesoft

    Mule ESB

    3.4, 3.6, 3.7, 3.8, 3.9, 4.1.x, 4.2.0, 4.2.1

    HTTP,

    JMS

    Yes

    Yes

    -

    Mule ESB Startup Settings

    Open SourceEclipse Vert.x verticles3.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

    -

    -

    -

    -

    -


    OracleJava Message Service 2.0JMSCorrelation of the listener
    is disabled by default 
    Yes

    Oracle

    Oracle AQ

    -

    JMS

    -

    Yes

    -


    OracleOSB deployed on WebLogic12.2.1

    HTTP

    JMS

    YesYes

    OSB Support

    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 HatHornetQ (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

    Spring Integration Support

    See also "Java Message Service Backends" on Java Backend Detection

    WSO2ESB4.7.0-YesYes- EUM Correlation is not supported

    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

    -

    Type IV

    Informix

    -

    Microsoft

    4

    Type II

    MS SQL Server

    2012

    Oracle MySQL, MySQL Community

    5.x

    Type II, Type IV

    MySQL

    5.x

    OracleRAC


    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
    AmazonDynamoDB -Exit Points-

    See "Amazon Web Services" on Java Backend Detection.

    AmazonSimple 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

    Apache

    Lucene - Apache Solr

    1.4.1

    Entry Points

    Yes

    Apache Solr Startup Settings

    JBoss

    Cache TreeCache

    -

    -

    -

    JBoss Startup Settings

    JBossInfinispan5.3.0+Correlation--

    Open Source

    Memcached

    -

    -

    -

    Memcached Exit Points

    Open SourceMongoDB Async Driver3.4-3.10--See "MongoDB Backends" on Java Backend Detection

    Open Source

    MongoDB Sync Driver

    3.1

    -

    -

    See "MongoDB Backends" on Java Backend Detection

    Open SourceMongoDB Reactive Streams Driver1.3-1.12--

    See "MongoDB Backends" on Java Backend Detection

    Oracle

    Coherence

    3.7.1

    Custom-Exit

    Yes

    Coherence Startup Settings

    Red Hat

    JBoss DataGrid---

    JBoss Startup Settings

    JBoss Cache TreeCache---
    JBoss Infinispan5.3.0+Correlation-

    Terracotta

    EhCache

    -

    -

    -

    EhCache Exit Points

    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-
    WebServices

    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-------
    ApacheRibbon
    HTTP Client
    2.1.0HTTP ClientYesYes (correlation)
    Entry - NA
    YesNAYes

    Apache

    Apache Thrift

    -

    -

    Yes

    Yes

    Yes

    Yes

    Yes

    Binary Remoting Entry Points for Apache Thrift
    EclipseJetty8.x, 9.xHTTP ClientYesYes (correlation only)Yes (ART supported)-YesSee "HTTP Backends" on Java Backend Detection

    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
    IBMWebsphere6.1, 7.x, 8.x, 9.xJAX-WSYes

    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 namingYes-
    JBoss

    7,8,11,16, and 18

    JAX-WSYesYes, detect and correlate. To enable correlation using a header transported in the SOAP:Envelope set node property enable-soap-header-correlation=true
    Web Service namingYes

    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

    java.net.Http

    -

    HTTP

    Yes

    -

    Yes

    Yes

    Yes

    See "HTTP Backends" on Java Backend Detection.
    Open SourceHTTPClient 0.3-3Oracle SOA (and potentially others that embed this library) -Correlation: Yes; Entry: NoYes-Yes

    Oracle WebLogic Startup Settings; also see Default configuration excludes WebLogic classes

    Open SourceGrizzly

    Grizzly Async HTTP Client (com.ning.http-client 1.8.x, 1.9.x, grizzly-http-client 1.1x)

    • NingAsyncClient v1 with NettyProvider, GrizzlyProvider
    • NingAsyncClient v2 with NettyProvider
    HTTP-Correlation: Yes; Entry:NoYes-Yes

    Oracle

    GlassFish Metro

    -

    JAX-WS

    -

    -

    -

    -

    -


    Oracle

    GlassFish Metro with Grails

    -

    JAX-WS

    -

    Yes

    -

    -

    Not by Default


    OracleJAX-WS RI2.3.1JAX-WS-To enable correlation using a header transported in the SOAP:Envelope set node property enable-soap-header-correlation=true-Web Service namingYes-
    Spring WSWeb Services3.x, 4.x, and 5.xHTTP, SOAP-To enable correlation using a header transported in the SOAP:Envelope set node property enable-soap-header-correlation=true-Web Service namingYes-

    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
    SquareOkHttp2.x, 3.x, 4.x (upto 4.22)HTTPYesCorrelation: Yes Entry: NoYes-Synchronous (2.x, 3.x, and 4.x upto 4.22) and Asynchronous (3.x and 4.x upto 4.22)

    -

    Web Services

    -

    SOAP over HTTP

    -

    Yes

    Yes

    -

    -

    Create Match Rules for Web Services

    "Web Service Entry Points" on Java Backend Detection

    jersey.github.ioReactive JAX-RS client API2.25+HTTP ClientYesYes (correlation) Entry – NAYesNAYes"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 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 Error Detection.