• EnglishEspañol日本語한국어Português
  • Inicia sesiónComenzar ahora

Java agent release notesRSS

April 26, 2021
Java agent v6.5.0

Download this agent version

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.

March 2, 2021
Java agent v6.4.2

Fixes

Fixes an issue that could cause some instrumentation modules (e.g. jax-rs-1.0) to have a WeaveViolation and not apply properly.

February 2, 2021
Java agent v6.4.1

Fixes

Fixes an issue in 6.4.0 where spans would not get sent to Infinite Tracing.

January 27, 2021
Java agent v6.4.0

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.

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.

December 17, 2020
Java agent v6.3.0

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

November 17, 2020
Java agent v6.2.1

Fixes

  • Fixes an issue where Spring-Webflux applications with endpoints returning Flux or empty content could become unresponsive

November 10, 2020
Java agent v6.2.0

New features

return serviceA.getData()
.map(service -> Response.builder().service(service).build())
.flatMap(serviceB::getData)
.flatMap(serviceC::getData)
.doOnNext(this::saveResponse);

Improvements

Fixes

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.

September 30, 2020
Java agent v6.1.0

Improvements

Java 15

  • The New Relic Java agent is now fully compatible with version 15 of the OpenJDK and Hotspot JDKs.

APIs

Fixes

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.

August 26, 2020
Java agent v6.0.0

Improvements

Fixes

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.

July 27, 2020
Java agent v5.14.0

Improvements

  • Agent Extensions The Java agent now provides a configuration to disable reloading extensions during runtime. extensions: reload_modified: false

  • Spring Webflux The Java agent now provides updated instrumentation for reactor-netty-0.8.0+ to link the Transaction across threads. In previous agent versions, Transactions would be named /NettyDispatcher.

  • Logging format To make the agent log easier to sort and read across locales, the date/time format has changed. The new format is log4j's ISO8610_OFFSET_DATE_TIME_HHMM and it is rendered like this in all locales:

    2020-07-10T08:33:00,328-0700 [9550 1] com.newrelic INFO: New Relic Agent: Loading configuration file "lib/./newrelic.yml"

    2020-07-10T08:33:00,423-0700 [9550 1] com.newrelic INFO: Using default collector host: collector.newrelic.com

    All other data on the log line remains the same.

Fixes

  • Solr instrumentation could throw a NullPointerException when Query.toString() returned null.

Copyright © 2024 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.