New features and improvements:
- Real-time profiling for Java using JFR metrics is now fully integrated into the Java agent. See the JFR core README for additional details.
This feature requires a supported version of Java 8 (specifically version 8u262
or higher) or Java 11 or higher and is currently disabled by default. To enable it set the following in your yaml (indented 2 spaces under the common section).
jfr: enabled: true
Notice: If you were previously using the jfr-daemon jar as an agent extension or standalone process you should remove that option to avoid potential conflicts with the JFR service that is now built into the agent.
- Not compatible with Java 7. In order to continue to innovate and efficiently provide new capabilities to our customers who run on the JVM, this and future agent versions aren't compatible with Java 7. If you're running Java 7, you may continue to use Java agent 6.5.0 or lower. For details, see this topic on the Explorers Hub.
- Adds support for akka http with Scala 2.13. #271
- Class annotation to trace lambda methods. #274
- Class annotation to trace methods by return type. #275
Fixes:
- Fixes an issue that could cause multiple versions of
akka-http-core
instrumentation to apply at the same time. #208 - The agent will now log dropped events at
FINE
instead ofWARN
to decrease verbosity. #296 - Fixes Javadoc comments that incorrectly stated that, when calling the
noticeError
API multiple times, the first error would be reported when in fact it's the last error that is reported. #313
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.
Known Issues
- OkHttp
This release contains a bug that breaks OkHttp versions 3.X and below. All affected users should upgrade to 7.0.1.
New features and improvements:
- The agent no longer bundles SSL certificates with it and the
use_private_ssl
option that configured the agent to use the previously bundled certificates has been removed. By default, the agent will use the SSL truststore provided by the JVM unless it is explicitly configured to use a different truststore with the ca_bundle_path option. See Configuring your SSL certificates for more details.
Fixes:
- Fixes an issue that could cause incorrect transaction naming when using JAX-RS sub-resources.
- Reactor Netty instrumentation improvements and fixes.
Deprecation notice
- Java 7 compatibility deprecation
In order to continue to innovate and efficiently provide new capabilities to our customers who run on the JVM, Java 7 support has been deprecated and this will be the last version of the agent compatible with it.
If you are running Java 7, you may continue to use Java agent 6.5.0 or lower.
For more information, see the Explorers Hub post.
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.
Fixes
Fixes an issue that could cause some instrumentation modules (e.g. jax-rs-1.0
) to have a WeaveViolation
and not apply properly.
Fixes
Fixes an issue in 6.4.0 where spans would not get sent to Infinite Tracing.
Note:
- There is an issue with this agent release that could lead to spans not being sent to Infinite Tracing. Please use 6.4.1 instead.
New Features and Improvements:
- Spring Webflux/Netty Reactor instrumentation improvements for enhanced tracing across asynchronous thread hops.
- The agent will now utilize a backoff sequence on connection retries to Infinite Tracing.
- New distributed tracing APIs have been added to better support general use cases for propagating distributed tracing headers. In particular the new APIs provide enhanced support for W3C Trace Context but are flexible enough to support other header protocols that may be supported by the agent in the future. Previous distributed tracing APIs have been deprecated and are subject to removal in a future agent release. See documentation here.
Transaction.insertDistributedTraceHeaders(Headers)
is used to create and insert distributed tracing headers (both newrelic and W3C Trace Context) into aHeaders
data structure.Transaction.acceptDistributedTraceHeaders(TransportType, Headers)
is used to accept the distributed tracing headers sent from the calling service and link these services together in a distributed trace.
Fixes:
- Updated the Java agent’s snakeyaml dependency to 1.27.
- In some environments the jar collector service could lead to high CPU utilization at application startup. The agent now provides a configurable rate limiter, with a reasonable default, for processing jars detected in the application’s environment. See documentation here.
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.
Improvements
- Spring Webflux
- The Java agent now supports Spring Webflux versions 5.3+
- Added reactor-netty.errors.enabled configuration to allow disabling error reporting in Subscriber::onError.
- Scala 2.13
- The Java agent now provides support for Scala 2.13 and frameworks compiled with 2.13 Akka-http, Play
Fixes
- The netty-4.0.8 instrumentation would sometimes not start a Transaction on channelRead, potentially affecting instrumentation dependent on it including: Spring, Akka and Play
- Updated the Java agent’s Apache HttpClient dependency to 5.13
- Spring Webclient could report the wrong URL when multiple HTTP calls to several URLs occurred in parallel
Fixes
- Fixes an issue where Spring-Webflux applications with endpoints returning Flux or empty content could become unresponsive
New features
- Adds support for Akka Http Core 10.2.0. Thank you jobicarter for reporting this issue.
- Adds support for gRPC 1.30.0. Thank you jef for submitting this request and trying it out.
- Adds support for
map
andflatmap
async external calls in spring webflux framework. Previously the agent didn’t support client calls that occurred within themap
orflatmap
methods within the spring webflux framework. External calls such asserviceB
andserviceC
in the example below would not get reported to New Relic:
return serviceA.getData() .map(service -> Response.builder().service(service).build()) .flatMap(serviceB::getData) .flatMap(serviceC::getData) .doOnNext(this::saveResponse);
- Adds support for Play 2.16.3. Many thanks to junder31 for this contribution.
Improvements
- The agent now supports parsing cgroup ids that do not contain
docker-
. Previously, the agent only supported docker cgroup ids that containeddocker-
in them, such as1:cpu:/system.slice/docker-12345abcde.scope
. The agent now supports parsing cgroup ids such as1:cpu:/system.slice/crio-12345abcde.scope
.
Fixes
- Prevents the agent from logging a timeout exception when using New Relic Edge with Infinite Tracing but the agent hasn’t sent spans in a while.
- Prevents the agent from logging a socket exception when trying to retrieve cloud provider information in a non-cloud environment.
- Adds New Relic EU certifications if
ca_bundle_path
is specified. This fix also came with the reintroduction of theuse_private_ssl
config, which can be set to add our agent certs to the truststore.
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.
Improvements
Java 15
- The New Relic Java agent is now fully compatible with version 15 of the OpenJDK and Hotspot JDKs.
APIs
- New Segment.addCustomAttribute(...) APIs have been added for adding attributes directly to spans.
- Newrelic.addCustomParameter API now supports boolean values
Fixes
- The agent would try to read environment variables using system-property syntax. It will now log the correct syntax and ignore the incorrect value.
Notes
- The Java agent now includes the newrelic.com SSL certificate. In previous agent versions, applications using a custom Truststore would have to provide their certificate or use the
use_private_ssl
configuration which was removed in 6.0.0. - Fixed an issue where applications could fail to start due to the agent attempting to access the JMX MBean server before it was initialized.
Improvements
- Register an MBean to expose the agent linking metadata.
- Support for okhttp 4.4 instrumentation.
- Improve reconnect behavior by not pinning to preconnected collector host instance.
Fixes
- Fix for asynchronous jar file collection. Collection of modules will no longer block the initial first harvest.
- Fix for Real Time Streaming. The first Real Time Streaming harvest will no longer be delayed by 30 seconds.
- Fix for
reactor-netty
verifier versions - Fix race condition around connection pool exhaustion by separating pool timeout from connection timeout.
Note re: certificate bundle use_private_ssl
This release removed the certificate bundle from the agent artifact. Users previously using use_private_ssl
should now use the ca_bundle_path
configuration directive. For more information, see the Java v6.0.0 release on GitHub.