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

Java agent release notesRSS

September 30, 2021
Java agent v7.3.0

Download this agent version

New features and 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 9, 2021
Java agent v7.2.0

New features and improvements

  • Scala Library Instrumentation #362 and #363

    • STTP versions 2 & 3 Akka-HTTP, HTTP4s and STTP core backends
    • Cats-effect v2
    • ZIO v1
    • HTTP4s client & server v0.21
    • Play 2.3-2.8
    • Akka-HTTP v10.1 & v10.2
    • For more information, see Scala instrumentation.
  • Scala API support (see PRs above)

    • Scala APIs provided for explicit instrumentation of several of above libraries in case auto-instrumentation is not desired
    • Cats-effect v2
    • ZIO v1
  • AWS v2 DynamoDB Instrumentation #343

  • GraphQL 16 Instrumentation #396

    • Create meaningful transaction names
    • Create meaningful spans
    • Reporting GraphQL errors
    • For more information, see GraphQL for Java
  • JFR feature causing excessive overhead when enabled JFR #203

    • Refactored code to use less memory.

Fixes

The existing MongoDB instrumentation was partially applying when MongoDB Reactive Streams is being used.

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.

July 15, 2021
Java agent v7.1.1

  • Real-time profiling for Java using JFR metrics

Due to overhead caused in some applications Real-time profiling for Java using JFR metrics is now disabled by default.

It can be enabled using the agent settings (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.

July 7, 2021
Java agent v7.1.0

Known issues

Some customers saw increased overhead when Real-time profiling is enabled.

See notice below on how to disable it.

New features and improvements:

  • Java instrumentation by XML new properties:

    • traceLambda - to trace lambdas inside a method
    • traceByReturnType - to trace all methods in a class that return a given type

    These are compatible with Java and Scala. For more information, see Java instrumentation by XML.

  • Scala APIs

    New artifacts allow Scala code to be instrumented using a fluent Scala API instead of the Java annotations. There are specific artifacts for versions 2.10, 2.11, 2.12, 2.13 of Scala. Scala 3.0 users can use the 2.13 artifact.

    For more information, see Scala instrumentation.

  • Real-time profiling for Java using JFR metrics

    This feature is now enabled by default.

    重要

    This feature will cause an increase in the consumption of data. The amount depends on the application. This feature can be disabled by adding the following to the agent yaml config nested under the common section:

    jfr:
    enabled: false

    For more information, see JFR core README.

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.

June 15, 2021
Java agent v7.0.1

Fixes

  • Fixes an issue where the agent would break OkHttp versions 3.X and lower. (#324)

June 9, 2021
Java agent v7.0.0

New features and improvements:

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 of WARN 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.

April 26, 2021
Java agent v6.5.0

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.

Copyright © 2024 New Relic株式会社。

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