• EnglishEspañol日本語한국어Português
  • ログイン今すぐ開始

Java agent release notesRSS

December 17, 2020
Java agent v6.3.0

Download this agent version

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.

June 16, 2020
Java agent v5.13.0

Improvements

  • Distributed tracing: With distributed tracing spans and/or Infinite Tracing, the Java agent will now incorporate additional information from the transaction event on to the root span event of the transaction.

  • New TracedMethod.addCustomAttribute(...) APIs have been added for adding attributes directly to spans.

    Note: Any attribute include or exclude settings specific to transaction events should be applied to your span attributes configuration or your global attributes configuration.

  • The Java agent now uses AWS's IMDS v2 to gather instance information.

Fixes

  • Jetty JMX metrics would not report when running embedded in Spring Boot.
  • Local configuration settings could revert to the default following an agent reconnect.

May 15, 2020
Java agent v5.12.1

Notes

Bug fixes

This is a patch release that resolves an issue in 5.12.0. With distributed tracing enabled and Infinite Tracing disabled, a defect in version 5.12.0 causes spans to be omitted from distributed traces.

Any customers currently on 5.12.0 are strongly encouraged to upgrade to this 5.12.1 patch release.

May 5, 2020
Java agent v5.12.0

New Features

Added support for Infinite Tracing on New Relic Edge.

Infinite Tracing observes 100% of your distributed traces and provides visualizations for the most actionable data so you have the examples of errors and long-running traces so you can better diagnose and troubleshoot your systems.

You configure your agent to send traces to a trace observer in New Relic Edge. You view your distributed traces through the New Relic’s UI. There is no need to install a collector on your network.

Infinite Tracing is currently available on a sign-up basis. If you would like to participate, please contact your sales representative.

Known Issue

In-process spans from Java services will not appear in distributed traces. All users should upgrade to 5.12.1.

Improvements

  • Spring

    Spring PatchMapping annotation will now be used to start and name transactions.

  • SQL

    Common Table Expressions in SQL Server, Postgres, and MySQL will report Datastore Metrics Datastore/<vendor>/statement/<first cte name>/with and Datastore/<vendor>/operation/with

  • Distributed Tracing

    Span events now report error attributes if an error occurs: TransactionError events will also contain a corresponding spanId attribute indicating where the error occurred.

Fixes

  • Solr Instrumentation could cause a NullPointerException in the agent logs for queries containing null parameters
  • The JAVA_ENV environment variable configuration has been deprecated. Use NEW_RELIC_ENVIRONMENT to set the environment configuration for the agent to use
  • The JDBC ResultSet instrumentation is now disabled by default internally. Applications configured solely via system properties and/or environment variables can enable with: -Dnewrelic.config.class_transformer.com.newrelic.instrumentation.jdbc-resultset.enabled=true or NEW_RELIC_CLASS_TRANSFORMER_COM_NEWRELIC_INSTRUMENTATION_JDBC-RESULTSET_ENABLED=TRUE
  • The quartz_job configuration did not affect applications using Quartz-2.0 and higher

March 18, 2020
Java agent v5.11.0

Improvements

  • Java 14

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

  • Java Flight Recorder

    A new Java Flight Recorder agent extension is now available to report real-time Java profiling metrics for application running on Java 14, including thread allocation, garbage collection and heap memory

Fixes

  • The agent would log a NullPointerException when trying to accept distributed trace payloads before it had connected to rpm.newrelic.com
  • Fixes an issue where W3C headers from New Relic’s .NET agent could produce malformed W3C traceparent headers
  • The agent now logs ForceRestartExceptions at warning level rather than severe
  • The noticeError API now supports reporting attributes of boolean and number types rather than their string representations

Copyright © 2024 New Relic株式会社。

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