Java agent v9.4.0

New features and improvements

• Removed linking metadata blob @NewFields from log4j-2.11 module 2917
• Added support for cluster mode in the lettuce-6.0 and lettuce-6.5 modules 2922
• Added new instrumentation modules for Vert.x web and core 5.x 2920
• Added new Java Server Faces instrumentation modules to replace legacy point cuts 2944
• Added a new Portlet module to replace legacy point cuts 2953
• Migrated shadow plugin from com.github.johnrengelman to com.gradleup 2945
• Added weave class instrumentation replacement for HandlerMethodInvoker3PointCut point cut 2967
• Removed @NewField annotations from the jdbc-generic module 2963
• Removed HandlerMethodInvokerPointCut point cut 2977
• Removed SpringPointCut point cut 2990
• Added new http.request.method attribute to all external HTTP spans 29853010
• Added support for decorating JFR data with APM labels (as configured in the java agent) 3007
• [Hybrid Agent] Decorated OpenTelemetry dimensional metrics with otlp_resource_attributes from connect response 2956

Fixes

• Fixed MDC leak issue in the apache-log4j-2.11 module 2926
• Removed java.rmi namespaced exceptions 2932
• Used Jakarta servlet exception attribute in the wildfly-27 module 2929
• Serverless mode now sent payload to the console if file pipe wasn't written 2975
• Changed ForceRestartException log to INFO 2989
• Added a new build time Patcher instance to remove problem enum values from the shadowed jspecify library @NullMarked class 2982
• Cleaned up segment instances for Netty Reactor HTTP calls 3004
• Fixed transaction linking metadata during some async operations 3006

Update to latest version

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

1. Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
2. Download the agent..
3. Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
4. Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
5. Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences

We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings.

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you're moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml.

Support statement:

• New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.