• EnglishEspañol日本語한국어Português
  • Log inStart now

Java agent release notesRSS

March 7, 2018
Java agent v3.47.1

Download this agent version

Bug fixes

  • A security update corrects an issue where the agent may report DB query results to New Relic or re-issue an SQL statement. For information on the bug fix, see the security bulletin.

Known Issues

Fixes in 3.48.0

  • Fixes an issue that in rare cases prevented Play async transaction tracking
  • Fixes a memory leak that could occur in Spymemcached instrumentation
  • Fix to disable attributes.include lists when High-security mode is enabled
  • Fixes an issue where errors outside of a transaction did not contain custom attributes on the event
  • Fixes an issue that caused the UI to not display errors that had error messages over 255 bytes

Fixes in 4.0.0

  • Fixes an issue where the Thread Profiler could fail to report. In this case, the agent logged a java.lang.StackOverflowError

Fixes in 4.1.0

  • Ensure that custom events added during a transaction do not get discarded if the transaction is ignored via a call to NewRelic.ignoreTransaction().
  • A security update that corrects an issue affecting PostgreSQL that could occur if High-security mode was enabled (or record_sql was set to off) and a query ran slow enough to trigger an explain plan. If the above conditions were met the agent may not have properly stripped out all information from the query. For information on this fix, see the security bulletin.
  • Fixes an issue where the agent could not parse database statements that included the IGNORE and INTO keywords.

Fixes in 4.2.0

  • Fixes a bug where transactions were being kept alive for too long when application is under heavy GC, causing inaccurate throughput to be reported.
  • Fixes a bug in which Akka routing instrumentation could cause extra memory usage. When this is the case, the transaction throughput will look significantly lower than anticipated.
  • Fixes a rare bug in Play WS instrumentation where exceptions thrown by instrumentation were propagated out to the application code, potentially causing the request to error.
  • Fixes a bug where Jersey Client and HttpUrlConnection could be double instrumented, resulting in inflated external call count.
  • Fixes a bug where the total time and response time for a long running task could be misreported.

Fixes in 4.3.0

  • Fixes an issue where transaction throughput counts could be artificially inflated when using async servlets in Jersey.
  • Fixes an issue where JBoss and Wildfly datasources could cause a LinkageError.

Fixes in 4.4.0

  • Fixes an issue where the Java agent 4.3.0 would not report data depending on the locale setting of the JVM. Java Agent 4.3.0 failed to send event data if the JVM locale is set to use a comma as the decimal. You would see NumberFormatException in the agent log.
  • Fixes a rare issue where the agent will incorrectly attempt to continually retransform classes when an extension with a modification date in the future is used, causing a significant increase in CPU load.
  • Fixes a ConcurrentModificationException caused by ning instrumentation that manifests in Mule instrumentation that causes the request it affects to be retried and the Java agent to not report header data.
  • Fixes an issue where if enable_auto_app_naming was set to true and distributed_tracing.enabled was set to true it would sample every distributed trace event. Now if the agent has both configs enabled, it will not turn on distributed tracing.

Fixes in 4.5.0

  • Fixes an issue where OKHttp 3 was not tracking external total time correctly.
  • Fixes an issue where for some JDBC drivers, the agent would execute additional getMetaData queries..
  • Fixes an issue with the agent’s Scala instrumentation that could result in incorrect throughput, invalid or negative data in transaction segments, or inability to ignore status codes.
  • Fixes an issue with the play-ws instrumentation that caused ClassNotFound exceptions to occur in the agent logs when withHeaders is used. This could result incomplete transactions and attributes in RPM.

Fixes in 4.6.0

  • Fixes an issue where the agent could cause an application deadlock when two tokens are created and linked from the other’s thread. This affects users of the New Relic token API and also users of the Hystrix framework.
  • Fixes an issue where the agent would not capture JMX Datasource information from Tomcat when JDNI GlobalNamingResources is used.

Fixes in 4.7.0

  • None

Fixes in 4.8.0

  • Fixed an issue where the agent would break webpage rendering by inserting New Relic Browser monitoring javascript into the <header> tag of pages which were missing <head> tags.
  • Certain frameworks, like Spring Cloud Gateway, triggered a bug in the Spring webflux instrumentation, causing transactions to stay open until they timed out. This bug resulted in more memory pressure and looked like a memory leak. This has been fixed in this release.
  • Fixed an issue where the agent would stop reporting to New Relic following a ForceDisconnectException and accumulate transaction data resulting in OutOfMemory Exceptions.
  • The agent now validates that app_names only contains three application names. If the agent is configured to report more than three application names, the agent will log a warning message and stop reporting to New Relic.
  • When a custom WSRequestFilter is used that modifies an outbound play-ws request, the agent would report overly long segments due to Segment timeouts and will also result in a loss of External/ metrics. This has been fixed.

Fixes in 4.9.0

  • Fixes a possible NullPointerException that could occur in Hystrix instrumentation and propagate into application code.

  • Fixes a bug where usage of the HttpsURLConnection getInputStream() method could cause some scoped external metrics to be double-counted.

  • Fixes an issue that prevents the agent from connecting to an HTTP proxy that does not requires a username or password.

    When configured to use an HTTP proxy by using proxy_host and proxy_port, the agent would look for proxy_username and proxy_password. If those weren't provided, the agent would use an empty string for proxy_username and proxy_password.

  • Prevents unnecessary dependencies from showing up in the newrelic-agent pom

  • Fixes deadlocks occurring in agent 4.7.0 that were caused by instrumentation of classes in the sun/nio/cs/.* package

  • Fixes an issue where custom jmx metrics with '.'s in the attribute name would not get recorded.

Fixes in 4.11.0

  • Fixes an issue where applications using neo4j bolt JDBC driver could fail to start.
  • "log_daily" configuration did not respect documented precedence
  • Fixes a bug that caused the Spring Webflux instrumentation to fail to apply for spring-webflux versions greater than 5.0.*
  • Fixes an issue where transactions would not be fully reported if distributed_tracing.enabled = true and cross_application_tracer.enabled = false
  • Fixes an issue where Akka Http application would not start with the agent attached when using sbt
  • Fixes an issue where the agent could fail to determine the Hostname

Fixes in 4.12.0

  • Fixed an issue with Jax-RS subresource transaction naming where the root path is duplicated when a nested resource structure is used. This could lead to transactions being named incorrectly for incoming requests to a Jax-RS framework.
  • Fixed a bug in the agent's Jetty metric sampling that could prevent Jetty specific metrics from being reported when the number of threads returned by JMX is zero.
  • Fixed a NullPointerException that can occur when Cross Application Tracing configuration is explicitly disabled.
  • Fixed an issue where transactions would be named incorrectly when using custom Akka Http stream directives or a pathEnd directive followed by a Segment directive.
  • Fixed an issue where certain usages of Akka and Scala would prevent transactions from being reported to New Relic. This would also manifest as a NullPointerException in the agent log at finest level.
  • The Java agent no longer includes Jaxb or Logback dependencies. A new dependency on Log4j2 has been added

Fixes in 4.12.1

  • Fixed an issue where an exception would be thrown during agent initialization which caused the application to shut down when the log file is not writable. In previous agent versions there was an undocumented behavior where the agent would log to STDOUT instead.
  • Fixed a regression where a NullPointerException would be logged and instrumentation would not be applied when using an XML extension with comments preceding the instrumentation section.
  • Fixed issue where setting the log_limit_in_kbytes greater than 0 and log_file_count equal to 1 would result in the agent not logging to the agent log file.

February 5, 2018
Java agent v3.47.0


  • Jersey Client

    The agent now provides instrumentation for Jersey Client versions 1.x and 2.x. You will see your calls using the Jersey Client APIs as Externals in New Relic, whether you are using the synchronous or reactive client API.

  • request.uri collected as an agent attribute

    You can now control the collection of request.uri on errors and transaction Traces you would other attributes. For more information on agent attributes see here.


  • Fixes a bug in Jersey 2 instrumentation where external segments could time out, causing an abnormally large "total time" for a transaction. This bug would occur if a client disconnected while being sent a response or if an unstable network is in place where an IOException occurs during response.
  • In some cases, the agent may have incorrectly reported the transaction thread name to New Relic as "New Relic Token Expiration Handler".
  • Agent was incorrectly bundling javax.xml and jregex packages
  • Fixes an issue in the Wildfly instrumentation that could cause async servlet transactions to go unreported.

January 8, 2018
Java agent v3.46.0


  • Websphere 9

With this release, the Java agent now supports Websphere 9, both Traditional and Liberty Profile.

More information on how to install and configure the Java agent on Websphere can be found here: IBM WebSphere Application Server.

Bug Fixes

  • Fixes a potential deadlock scenario caused by the Java agent in high throughput applications running on Vert.x.
  • Usage of the setNull() method on the JDBC interface now reports up null in the query string sent to New Relic, instead of incorrectly reporting up the sqlType as the value.
  • Fixes a JVM crash that can occur when running the Java agent with the non-default spring-aop-2 instrumentation enabled.

December 11, 2017
Java agent v3.45.0


  • RabbitMQ

The agent now provides instrumentation for RabbitMQ 5.0.


  • This release changes instrumentation for all supported versions of RabbitMQ to use the exchange name instead of routing keys for the transaction name and produce/consume metrics. This should provide more meaningful transaction names, but will change what transactions you see in New Relic.

  • Now reports queue purge

  • No longer reports misleading MessageBroker consume metric for callbacks/message listeners

  • Adds message properties to tracer attributes, and a configuration to disable them:

    enabled: false

Bug Fixes

  • Exceptions thrown within scala Future/CallbackRunnable code could cause inaccurate transaction times
  • Deadlock could occur when tracking asynchronous activity in Vert.x.

November 7, 2017
Java agent v3.44.1


If you are using Akka Http 10.x, use this 3.44.1 release rather than 3.44.0.

Bug Fixes

  • Fixes an issue where an Akka HTTP 10.x application could fail at runtime with a NullPointerException.

November 6, 2017
Java agent v3.44.0

Known Issue

This release contains a bug that could cause an Akka HTTP 10 app to fail at runtime with a NullPointerException.

Please use version 3.44.1 instead.


  • Supports Play 2.6, Akka HTTP 10, and Scala 2.12.

The agent now provides instrumentation for Play 2.6.x. It also provides instrumentation for Akka HTTP 10. It supports Scala 2.12.x, so Play and Akka HTTP transactions show full detail, including async activity using Scala Promises and Futures.

  • Lowers overhead for Play, Akka, and Scala.

This agent release imposes lower overhead for applications that use Play, Akka, and Scala. The reduction in overhead will be most notable in lightweight applications and microservices.

Unlike previous versions of the agent, by default the agent will not report Scala Futures as transaction segments, and those Futures will not contribute to the transaction’s reported Total Time. For most customers, this change will provide more concise information in transaction trace details, with no loss of insight. If those segments are valuable to you, and you are willing to incur higher overhead, you can enable that instrumentation with the following setting:

enabled: true

Bug Fixes

  • The 3.43.0 version of the agent caused Tomcat to report a ClassFormatException error at startup. The error did not affect the application or agent.
  • High-throughput applications with daily logging enabled and a specified log limit could cause log files to grow without bound.
  • The agent could leak memory when instrumenting the Ning Async Http Client.
  • Akka HTTP content type was not reported.

September 27, 2017
Java agent v3.43.0


  • Java 9

    The Java agent can now be run with Oracle Java SE 9! You can run your applications on the Java 9 runtime JVM, and run applications compiled at the Java 9 language level.

    By default, this release of New Relic's Java agent does not support applications configured for the new Java 9 modular mode, such as Jigsaw. In order to run in this mode with the agent, your application must be configured to require the java.sql module through one of these two options:

    • Add requires java.sql; to your module-info.java class
    • Use the --add-modules=java.sql command line flag

August 28, 2017
Java agent v3.42.0


  • Hystrix

    With this release, the Java agent now supports Hystrix version 1.5.

  • Improved metadata collection for cloud providers

    The agent now collects additional metadata when running in AWS, GCP, Azure, and PCF. This information is used to provide an enhanced experience when the agent is deployed on those platforms.

Bug Fixes

  • Fixed bug that caused agent to not report error rate metrics. The UI would show application errors, but error rate would show up as 0%. This was introduced in 3.38.0.
  • Improved Hystrix transaction reporting to better handle cases where an Observable is created that never executes.
  • Fixed an issue where JAX-RS subresources would not be picked up for transaction naming, resulting in an incorrect or incomplete transaction name.
  • Fixed a bug with DataNucleus that was preventing instance level and query information from being picked up.
  • Fixed a bug that caused the agent to report external calls made with Commons HTTPClient as "unknown host".

Known Issues

  • Fixed in 3.44.0

    • High-throughput applications with daily logging enabled and a specified log limit could cause log files to grow without bound.
    • The agent could leak memory when instrumenting the Ning Async Http Client.
    • Akka HTTP content type was not reported.
  • Fixed in 3.46.0

    • In rare cases, a Vert.x application running this version of the agent can deadlock.
    • Usage of the setNull() method on the JDBC interface now reports up null in the query string sent to New Relic instead of incorrectly reporting up the sqlType as the value.
    • JVM crash that can occur when running the Java agent with the non-default spring-aop-2 instrumentation enabled.

July 25, 2017
Java agent v3.41.0


Bug fixes

  • Fixed bug in Netty instrumentation that cause erroneous reporting of NettyDispatcher transactions. This affected transactions responding large incoming requests.
  • Fixed bug that caused agent to not report error rate metrics. The UI would show application errors, but error rate would show up as 0%. This was introduced in 3.38.0.

June 26, 2017
Java agent v3.40.0


  • DynamoDB The Java agent now provides visibility into your applications’ usage of DynamoDB when using the client versions 1.11.106 and greater. You will see the calls in the application breakdown, in trace details, on the Databases page, in Transaction maps, and in Service maps.
  • Solr With this release, the java agent now supports Solr versions 6.5.0+.

Bug Fixes:

  • Fixed an instrumentation gap that prevented agent from capturing instance-level information about database queries for non-blocking IO driver configurations.
  • Fixes an issue where usage onCompleted handler(s) with the ning async http client could cause a transaction to end too early, resulting in missed instrumentation.

Copyright © 2024 New Relic Inc.

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