Incompatible changes

To improve security, we’ve made changes to how the agent handles incoming URLs. These changes may affect the agent’s behavior because not-enforced rules and AM policies are evaluated against normalized paths with the path parameters removed.

Learn more about these changes in URL handling.

The common REST monitoring endpoint has been removed. Use the Prometheus endpoint for monitoring your deployment.

To improve security, the audit handling code is deprecated and replaced by the Commons Audit Framework.

To prevent logging of sensitive data for an audit event, the Commons Audit Framework uses a safelist to specify which audit event fields appear in the logs.

By default, only safelisted audit event fields are included in the logs. To include and exclude elements from JSON audit events, use Audit Log Include Paths and Audit Log Exclude Paths.

The agent.jar isn’t required for drop-in software update to Java Agent 2023.9. If the file is present in the container, delete it as described in Tomcat Java Agent software update.

You must now provide the full path to jee-agents-sdk-version.jar in the module.xml file for drop-in software update to Java Agent 2023.9. The following libraries are no longer required:

For more information, refer to JBoss and WildFly Java Agent software update.

The agent.jar file isn’t required for drop-in software update to Java Agent 2023.9. If the file is present in amlogin.mod, delete it as described in Jetty Java Agent software update.

The following libraries aren’t required for drop-in software update to Java Agent 2023.9:

For more information, refer to WebLogic Java Agent software update.

Support for JDK 8 has been removed.

WebLogic 12c Java Agent and WebSphere Java Agent do not support JDK 11, which is the minimum JDK version supported in this release. Consequently, these platforms are not supported in this release. Use Java Agent 5.10 or an earlier version for these platforms.

Log messages in Java Agent and third-party dependencies are now recorded using the Logback implementation of the Simple Logging Facade for Java (SLF4J) API.

From this release, TRACE is the highest log level. In previous releases, ON was the highest log level.

From this release, when the log level is ON, TRACE level logs are written to file. In previous releases, TRACE level logs were written to the standard output.