Java agent v6.4.0

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.

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 a Headers 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.

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.

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.