Java agent release notes

Java agent v1.3.0

Thu, 17 Mar 2011 00:00:00 +0000

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes:

Component-based transaction naming
Agent API
Multiple applications enhancements
Send data to RPM in UTF-8 format
Bug fix: ClassCastException setting record_sql: off

Java agent v1.4.0

Mon, 11 Apr 2011 00:00:00 +0000

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes:

Real User Monitoring
Bug fix: setting 'ignore_status_codes' to a single value is ignored

Java agent v2.0.1

Mon, 23 May 2011 00:00:00 +0000

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Bug fix: JBoss fails to start with JMX errors (introduced in 1.4.0)

Java agent v2.0.0

Mon, 09 May 2011 00:00:00 +0000

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Auto Real User Monitoring
Support for X-Request-Start, X-Queue-Start, and X-Queue-Time request headers
Bug fix: newrelic-api.jar does not work with Java 1.5
Bug fix: NullPointerException instrumenting HttpClient
Bug fix: setting request attribute "com.newrelic.agent.TRANSACTION_NAME" not working (broken in 1.4.0)
Bug fix: uncaught exceptions not logged during startup
Bug fix: thread profiling fails if CPU time not supported
Bug fix: error is ignored only if it is the root cause

Java agent v2.0.2

Thu, 16 Jun 2011 00:00:00 +0000

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Bug fix: Auto RUM compiler error instrumenting some JSPs
Bug fix: Auto RUM should inject header after meta tags
Bug fix: Installer does not modify start script if another javaagent switch is present
Bug fix: Agent breaks request URI parsing in Tomcat: JSESSIONID not removed (introduced in 1.4.0)
Bug fix: Some compilers unable to compile JSP with auto RUM
Installer support for Glassfish

Java agent v2.0.3

Thu, 04 Aug 2011 00:00:00 +0000

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Bug fix: RUM: Tag files not compiling in Jasper
Bug fix: RUM: header not always inserted after meta tags
Bug fix: NullPointerException if filter config is null
Bug fix: Fix IE measurement problem in RUM footer
Bug fix: API calls should not throw exceptions

Java agent v2.0.4

Tue, 30 Aug 2011 00:00:00 +0000

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Bug fix: RUM: handle duplicate injection of our JS header and footer
Bug fix: fix the license key hint that is inserted into the auto-generated configuration file
Allow logging to standard out
Allow configuration of the agent via environment variables

Java agent v2.10.0

Wed, 31 Oct 2012 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Instrumentation of Servlet 3.0 async processing. Processing initiated by startAsync is included in metrics and transaction traces.
Custom instrumentation configured through an XML file. For details see the documentation.
Request attribute for setting app name now allows multiple app names
Bug fix: auto RUM inserts header and footer into script tags

Java agent v2.1.0

Fri, 07 Oct 2011 00:00:00 +0000

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Report slow SQL statements
Performance improvements
Continue to record metrics after transaction trace limit is reached
Bug fix: never drop data
Bug fix: Agent destructively reads request parameters in Resin
Bug fix: default transaction trace threshold should be apdex_f
Bug fix: Don't obfuscate digits in SQL statements that are part of table name

Java agent v2.11.0

Wed, 28 Nov 2012 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Support Jetty Continuations
Support Servlet 3.0 async API for WebSphere
Bug fix: java.lang.ClassCircularityError in JBoss
Bug fix: Agent does not detect Solr 4.0
Bug fix: NewRelicIgnoreApdex annotation ignored

Java agent v2.1.2

Mon, 07 Nov 2011 00:00:00 +0000

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Performance improvements
Bug fix: parse inner select SQL statements
Bug fix: execute SQL statement not recognized

Java agent v2.10.1

Tue, 13 Nov 2012 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Remove stall detection

Java agent v2.12.0

Thu, 06 Dec 2012 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Agent reports jars used by applications to the Environments tab in the UI

The Environments tab in the New Relic UI now shows the jars used by your application.
Fix: In certain cases, auto-RUM of JSP breaks HTML

An angle-bracket in quotes in a META tag causes the agent to produce invalid HTML for JSP. The fix produces valid HTML for this case.
Fix: Key Transaction ApdexT value not used

In v2.10 - v2.11, the application-level ApdexT value is used for Key Transactions rather than the ApdexT for the Key Transaction itself. In this release, the ApdexT for the Key Transaction is used.
Fix: With OC4J using PolicyClassLoader, no metrics displayed

In the case where OC4J uses the PolicyClassLoader, the agent generates a java.lang.StackOverflowError in the log and does not provide metrics. In this release, the error does not occur.
Fix: External metrics for HttpClient include port if host is an IP address

In the case where an external service call uses HttpClient with an IP address rather than a hostname, the port number is also included. In this release, the port number is not displayed.

Java agent v2.13.0

Wed, 16 Jan 2013 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Agent can be configured to not send JVM arguments to the New Relic server

The property send_jvm_props can be set to false, which will cause JVM arguments to no longer be sent to the server. Use this setting if you set sensitive system properties on the command line.
Agent reports full URL in external service calls for transaction traces

The agent now will provide the full URL if available in transaction traces for external calls.
Fix: ResinServletTracerFactory no longer causing SkipServletTracerFactory errors

When hitting the ResinServletTracerFactory inside a transaction, a SkipServletTracerFactory excetion will no longer be thrown.
Agent logging improvements

We have improved the clarity of logging messages, adjusted logging levels to be more appropriate, and increased logging performance.

Java agent v2.14.0

Fri, 08 Feb 2013 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Fix: New Relic includes property take_last_status to only grab the final http status code.

By default, New Relic reports any error status code. However, when this property is set to true, only the last http status code will be reported. This property should be set when using Apache Felix.
Fix: New Relic now correctly patches Apache Felix ClassLoaders.
Fix: Time will now display correctly for the first hour of the day when using log4j.
Fix: RUM header was missing a semicolon at the end of the last statement. Some browsers prefer semicolons everywhere.
Adds a X-NewRelic-ID header to outbound requests using the Apache HttpClient or HttpURLConnection libraries. This change helps improve the correlation of performance between services in a service-oriented architecture for a forthcoming feature. In the meantime, if you wish to disable the header, set 'cross_application_tracing: false' in newrelic.yml.
Fix: Java agent now reports hostnames consistent with the output of "hostname -s" to match all other agents
Add report of physical server memory (in addition to JVM memory) on Unix/Linux machines

Java agent v2.14.1

Fri, 15 Feb 2013 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Fix: Application errors using java.net.HttpURLConnection. The bug, introduced in 2.14.0, could cause errors in code that uses java.net.HttpURLConnection. Possible errors could occur in XML parsing, incorrect http response status, or BeanCreationException in Spring. As part of this fix the agent does not add a 'X-NewRelic-ID' header to outbound requests using java.net.HttpURLConnection.

Java agent v2.15.0

Thu, 28 Feb 2013 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Cross Application Tracing

The Cross Application Tracing feature adds request and response headers to external calls using the Apache HttpClient libraries to provided better performance data when calling applications monitored by other New Relic Agents (Java, .NET, and Ruby, with others coming soon).

The 2.14.0 release links aggregated data across applications. This release also links transaction traces.

The configuration setting introduced in 2.14.0 to enable/disable Cross Application Tracing in newrelic.yml has changed. The old setting: 'cross_application_tracing: true' is deprecated. The new setting is

cross_application_tracer:
enabled: true

The default setting is true. Set to false to disable Cross Application Tracing.
Instrumentation added for the AmazonS3Client version 1.x

The New Relic Agent now offers support for version 1.0 to current of the com.amazonaws.services.s3.AmazonS3 interface.
New Relic Java Agent support a daily roll over log

To roll over the agent log every day, set the property log_daily to true. Set the property log_file_count to the number of day logs you would like to keep.
New Relic Java Agent now communicates with New Relic via HTTPS by default rather than HTTP

If you have an existing installation and wish to use HTTPS to communicate with New Relic, edit your newrelic.yml file to include

ssl: true

in the common section. We recommend this for existing customers in order to improve the security of your communications with New Relic.
Java Agent installer improvements

The Java Agent installer now supports JBoss 7.x AS and JBoss 6.x EAP in standalone mode. Instructions for manually installing the Java Agent on JBoss 7.x AS and JBoss 6.x EAP can be found at https://newrelic.com/docs/java/installing-the-java-agent-on-jboss.
Fix: Default hostname reported

This release reverts the change in 2.14.0 that effected the way that the hostname is reported. With this release, the agent reports the default hostname rather than short form in order to correlate with New Relic server monitoring.
Fix: Web transactions naming in Spring MVC version 3.x

This bug caused customers using Spring 3.0.1 and above to often have web transactions named by the servlet rather than controller method. This has been fixed such that a separate metric is created for each controller method.

Java agent v2.15.1

Wed, 13 Mar 2013 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Fix: Cross Application Tracing does not correlate consistently when using Tomcat 6+

Cross Appplication Tracing did not correlate calling and called applications when the called application ran in Tomcat 6 or later and the HTTP response was greater than about 7k.

Java agent v2.16.0

Mon, 25 Mar 2013 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Adds a stack trace in the transaction trace for slow methods.

This change provides additional insight into your slowest transactions.You can adjust how slow a method is before it generates the stack trace by setting stack_trace_treshold (in seconds).
```
transaction_tracer:
  stack_trace_threshold: 1.0
```
Cross Application Tracing support for HttpURLConnection.

Adds request and response headers to external calls using the HttpURLConnection library to provided better performance data when calling applications monitored by other New Relic Agents (Java, .NET, and Ruby, with others coming soon).
Fix: Cross Application Tracing does not correlate consistently when using WebSphere, WebLogic, Resin, and Glassfish.

Cross Appplication Tracing did not correlate calling and called applications when the HTTP response was large.
Queuing time more broadly supported.

The 'X-Queue-Start' and 'X-Request-Start' request headers for Heroku and other frontend web servers are interpreted and reported. Previously, queuing time was not reported for Heroku.
Work-around for Oracle JVM bug that in rare cases causes a native memory leak

In rare cases, the Oracle JVM can leak native OS memory (not heap space) when classes are intercepted by the agent. This setting turns off interception of classes that are loaded after the given number of seconds. The agent will continue to monitor classes loaded before this time.
```
class_transformer:
  shutdown_delay: 3600
```

Java agent v2.17.1

Fri, 12 Apr 2013 00:00:00 +0000

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Fix: Reverted transaction naming change on ColdFusion, introduced in 2.17.0.

That change caused issues with certain modes of ColdFusion.

Java agent v2.17.0

Thu, 11 Apr 2013 00:00:00 +0000

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Agent reports JDBC ResultSet query time

This change gives you deeper insight into your database time by displaying ResultSet processing time in aggregate metrics and transaction traces.
Fix: Avoid retransform exception on IBM JREs

In some IBM JRE versions, the agent logged an INFO level exception and did not instrument select classes. This fix allows these classes to be instrumented properly.
Adds a stack trace in a transaction trace for all methods taking longer than stack trace threshold. This differs from 2.16 which only provided stack traces for a limited number of methods.
Better transaction naming on ColdFusion

Java agent v2.17.2

Wed, 17 Apr 2013 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Fix: Fixed bug in which application code can throw NoSuchMethodError

In some cases using Java agent 2.17.0 and 2.17.1, application code was throwing an exception

java.lang.NoSuchMethodError: java.lang.Boolean.valueOf(B)Ljava/lang/Byte;

This usually occurred when calling a ResultSet implementation.

Java agent v2.18.0

Tue, 07 May 2013 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

New metrics are displayed under the JVM tab

While the metrics displayed differ between application servers, common metrics include loaded class count, active thread count, active thread count per thread pool, active session count per application, and active transaction count. In order to see these metrics, JMX must be enabled on your app server.
Fix: When naming transactions, the property enable_auto_transaction_naming should be honored

There was an issue where transactions using the Spring Framework were ignoring the property.
Fix: Strip query string from HTTP Referer

Query strings can potentially contain sensitive information. To prevent that data from being sent to New Relic, only the host and path portion of the referer are captured.

Java agent v2.19.0

Wed, 29 May 2013 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Play 2 Instrumentation

Provides insight into Play 2.x Java and Scala applications. Adds instrumentation to Netty server, Akka actor calls, Scala Promises and Futures, and the WS API calls.

Known issue: Request parameters are not captured properly even if capture_params is enabled.
Support added for Jetty 9 (tested on 9.0.0 through Jetty 9.0.3).
Fix: Agent can cause java.lang.VerifyError on code compiled with Java 7

In certain cases, if your application code or third party libraries are compiled with Java 7, you may get a java.lang.VerifyError. This fix allows the agent to work correctly in those cases.
Fix: The Java Agent detects status codes for Apache Felix correctly by default. The property take_last_status is now deprecated.

Java agent v2.2.0

Tue, 06 Dec 2011 00:00:00 +0000

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Performance improvements
Support server-side configuration
Bug fix: byte-code instrumentation causes class loading deadlock and OS memory explosion

Java agent v2.19.1

Fri, 14 Jun 2013 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Fix for 2.19.0 known issue: Play now captures GET and POST parameters correctly if capture_params is enabled.
Disabled overly ambitious instrumentation used to time template rendering for Play 2. Resulted in unintended classes being instrumented.

Java agent v2.20.0

Mon, 01 Jul 2013 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Glassfish 2.1 JVM tab: The JVM tab will now show thread, session, and transaction metrics for Glassfish 2.1.
Fix: Solr cache metrics: The solr cache metrics do not appear with versions 2.18 and 2.19 of the agent. This has been fixed, and all solr metrics should now appear.
Fix: NullPointerException in New Relic agent logs when NewRelic API called: In certain circumstances, a call to a method on the NewRelic class can generate a NullPointerException in the agent logs. It does not cause a NullPointerException in your application.
Fix: Support custom extension XML file for WebSphere with JRE: Prior to this fix, an attempt to use a custom extension XML file with a IBM JRE would lead to a ClassNotFoundException.

Java agent v2.21.0

Wed, 07 Aug 2013 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

X-Ray sessions

Adds support for X-Ray sessions. An X-Ray session collects Transaction Traces and a thread profile for a Key Transaction.
Fix: In 2.20.0 an @Trace annotation ignored the transaction for Apdex

An @Trace annotation on a method called in a web transaction had the side-effect of ignoring the transaction for calculating the Apdex score.
Fix: HTTP status code for Errors

If the HTTP status code for a web transaction was less than 400, the HTTP status code reported in the error was 500. The actual status code for the web request is now reported.
Fix: Spring exception handling

The Exception argument in the Spring DispatcherServlet processHandlerException method was reported as an Error with an HTTP status code of 500. The actual status code in the HTTP response is now reported.
Fix: Reading Post Parameters for Resin 3

Prior to this fix, post parameters in Resin 3 were always read using the default properties even if the application tried to read the post parameters using non-default properties or by just grabbing the request input stream.
Fix: JVM Tab Metrics Not Showing up for Tomcat Applications

Prior to this fix, if the service name in service.xml was not Catalina, then metrics would not appear under the JVM tab. Additionally, if you are using an embedded Tomcat 5/6, metrics should now appear under the JVM tab.
Fix: Improved compatibility with Java 1.5

In the custom xml validator, there were references to String.isEmpty() which was not available until Java 1.6. Those have been removed.
Fix: Reducing DNS problems by not automatically adding '.' to the domain name

By default the '.' is included. But if changed, then the '.' won't be added.
Fix: JVM tab metrics showing for all Applications In JVM

Metrics under the Thread, Session, and Transaction tabs used to only appear under the main application. The data will now be shown for all applications running in the specific JVM.
Fix: Using a Proxy now works with SSL Enabled

In prior releases proxy authentication would fail when SSL was enabled. We now do proxy authentication using the java.net.Authenticator.
Fix: Akka error reporting

If an actor throws an exception or the message times out, an error is reported. Previously, no error was reported.

Java agent v2.2.1

Thu, 29 Dec 2011 00:00:00 +0000

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Bug fix: ClassFormatError and NoClassDefFoundError instrumenting proxy classes
Bug fix: transaction trace threshold not working (introduced in 2.2.0)
Bug fix: infinite loop instrumenting parameterized SQL statements

Java agent v2.21.1

Fri, 09 Aug 2013 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Fix: In 2.21.0, calls to NewRelic class can cause NoClassDefFoundError

In 2.21.0, if your application calls the NewRelic class and does not include the newrelic-api.jar, the application would throw a NoClassDefFoundError. With this fix, the separate newrelic-api.jar is not required. However, it is recommended that your application include the newrelic-api.jar so that calls to the NewRelic API resolve with or without the agent installed.

Java agent v2.21.2

Sat, 10 Aug 2013 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Fix: Longer application startup time

Release 2.21.0 introduced an issue that could cause application startup to be slower than in previously releases. This fix returns application startup time to normal.
Fix: File location changes

Release 2.21.0 introduced a change to file locations within the newrelic zip file. This fix reverts the locations to what they were previously.

Java agent v2.21.3

Tue, 13 Aug 2013 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Fix: Agent did not run with J2SE 5.0 (aka JDK 1.5)

Release 2.21.0 - 2.21.2 did not run correctly on J2SE 5.0. On startup, the agent reports:
```
Unable to start New Relic agent: java.lang.UnsupportedClassVersionError: Bad version number in .class file
```
If you are running J2SE 5.0, please update to agent version 2.21.3.

Java agent v2.21.4

Tue, 10 Sep 2013 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Fix: Metric Grouping Issue with Netty

The request URL was referenced in some metric names, causing Metric Explosion. The URL is no longer included in the metric name.
Fix: Make Cookie parsing more robust when running on Netty

Cases where the Cookie header was malformed were causing exceptions to be thrown. Agent now makes a better effort to capture the individual valid parts.
Fix: Agent could not connect to New Relic in non-DNS environments

Fixed an issue which caused the agent to only be able to connect to New Relic in environments where DNS was used for hostname resolution.
Fix: In 2.21.2 and 2.21.3 an @Trace annotation ignored the transaction for Apdex

An @Trace annotation on a method called in a web transaction had the side-effect of ignoring the transaction for calculating the Apdex score.

Java agent v2.21.6

Thu, 24 Apr 2014 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End of life policy.

Notes

Note: This is a bugfix release for the legacy Java SE5 version of the agent. Unless you are a Java SE5 user, use the latest version of the agent.

The 3.x agent works with Java SE 6 and 7. If you are using Java SE 5, this is the release for you.

Fix: XML entity expansion with non-SSL connection to New Relic

Fixed an XML entity expansion vulnerability that only occurs when the agent is configured with ssl: false; the default is true. The agent already has other protection against unauthorized entity expansion. This fix is an additional layer of protection.

Java agent v2.21.5

Wed, 05 Mar 2014 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

The 3.x agent works with Java SE 6 and 7. If you are using Java SE 5, this is the release for you.

PostgreSQL explain plan bug

There was a PostgreSQL bug that allowed parameters to be sent in explain plans under some circumstances. To avoid this issue, the New Relic agent now does not report explain plans for PostgreSQL.
Agent no longer supports obfuscation of individual fields

Previous versions of the agent allowed an obfuscatedsql_fields option to select specific field names to obfuscate when record_sql: raw. We have discovered rare cases in which this feature would not mask SQL parameters correctly, so we have removed the configuration option. Now, if obfuscated_sql_fields is set, the setting of record_sql: raw is ignored and _all fields are masked.
Fix: SQL parameter obfuscation didn't work if the parameter value contained a newline

The record_sql: obfuscated config setting did not properly mask parameters when it included a newline character. This bug has been fixed.
Fix: Private trust store location for use_private_ssl flag

The 2.21.4 agent did not properly load a private trust store used with the use_private_ssl flag. This bug has been fixed.

Java agent v2.21.7

Thu, 08 Jan 2015 00:00:00 +0000

Download this agent version

Fixes

This is a bugfix release for the legacy Java SE5 version of the agent. Unless you are a Java SE5 user, use the latest version of the New Relic Java agent.

Fixed an issue that in rare cases could cause the agent to cease reporting data until JVM restart.

Known issues

X-ray sessions sometimes return no transaction traces. Many x-ray session runs can cause a memory leak.
Play framework
- Higher overhead with Play 2 than later releases.
- Does not work properly with Play 2.2
- Counts akka.actor.ActorKilledException as an error.
- Play transaction does not complete until timeout expires
- When using Play, ignoreTransaction call does not take effect
In some cases running Weblogic, the Java agent fails certificate validation when connecting to New Relic. This may require a workaround.
This release contains some inconsistencies in the instrumentation of Hibernate across versions.
This release requires a workaround to use SSL with WebSphere.
Potential memory leak when app continually creates ClassLoaders.
Rare memory leak if agent does not report to New Relic for an extended period.
When running IBM JVM without WebSphere, you must set the sync_startup flag set to true in the common section of newrelic.yml: sync_startup: true.

Workaround

If you require a workaround for one of these issues, please open a ticket at support.newrelic.com.

Java agent v2.3.0

Wed, 01 Feb 2012 00:00:00 +0000

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Play! framework support
Create web transactions using custom instrumentation
Use log4j instead of Java API logging
Bug fix: RUM auto instrumentation fixes
Bug fix: multiple app names in app_name setting out of order (introduced in 2.2.0)
Bug fix: possible java.lang.IllegalArgumentException with parameterized SQL (introduced in 2.2.0)
Bug fix: WebSphere instrumentation broken (introduced in 2.2.0)

Java agent v2.3.1

Mon, 13 Feb 2012 00:00:00 +0000

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Bug fix: Agent logging breaks webapp log4j configuration (introduced in 2.3.0)

Java agent v2.4.0

Tue, 27 Mar 2012 00:00:00 +0000

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Bug fix: ClassNotFoundException with JBoss AS 7 (introduced in 2.2.0)
Bug fix: NoClassDefFoundError with Glassfish 3.1.2 (introduced in 2.2.0)
Bug fix: ClassCastException with Glassfish 3.1.1 (introduced in 2.2.0)
Bug fix: Agent stops reporting web transactions (introduced in 2.2.0)
Bug fix: Instrumentation error in Jetty 7.5.4 (introduced in 2.2.0)
Bug fix: possible unknown host for external call with HttpClient 3.0.1 (introduced in 2.3.0)
Bug fix: stall error reporting broken
Bug fix: agent_enabled setting not working
Add stall_threshold setting for reporting stall errors

Java agent v2.4.1

Mon, 02 Apr 2012 00:00:00 +0000

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Bug fix: AssertionError in WebLogic (introduced in 2.2.0)

Java agent v2.4.2

Wed, 18 Apr 2012 00:00:00 +0000

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Bug fix: ClassLoader.loadClass deadlock (introduced in 2.4.0)

Java agent v2.5.0

Tue, 01 May 2012 00:00:00 +0000

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Browser traces
Bug fix: OC4J does not start (introduced in 2.2.0)
Bug fix: AbstractMethodError calling getRemoteUser in Tomcat and Glassfish
Bug fix: Deployment does not use SSL port if SSL is configured (introduced in 2.2.0)
Bug fix: NullPointerException getting request URI in Jetty 4.x and 5.x
Bug fix: JSP compiler error with auto RUM in Tomcat 5
Bug fix: Transaction parameters removed if error is reported but response status < 400
Bug fix: No request parameters in Resin 3.x
Bug fix: AbstractMethodError calling getContextPath() with Tomcat 5.x (introduced in 2.2.0)
Bug fix: Ignore transaction before transaction started stops transaction reporting

Java agent v2.6.0

Wed, 06 Jun 2012 00:00:00 +0000

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Java 7: Native support for instrumenting classes compiled to Java 7 bytecode
Audit Mode: mode which logs all data sent to New Relic in the newrelic_agent.log
Bug fix: Prevent agent instrumentation from changing the Serial Version UID (introduced in 2.2.0)
Bug fix: Prevent memory leak when client applications start and subsequently stop a thread before completing a transaction (introduced in 2.2.0)
Bug fix: Prevent stack overflow exception when executing queries using the Postgres 9.0.x JDBC driver
Bug fix: Fix dispatch handler instrumentation for Jetty 7.5.* (introduced in 2.5.0)
Bug fix: Set the application port correctly under Jetty 4.*
Bug fix: Make the transacation_tracer configuration settings respect command line and environment overrides

Java agent v2.7.0

Tue, 31 Jul 2012 00:00:00 +0000

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Add skipTransactionTrace element to @Trace annotation to tell Agent to drop method from transaction trace
Add -Dnewrelic.bootstrap_classpath=true system property to append newrelic.jar to bootstrap classpath
Support RUM reporting to multiple applications (RUM3)
Bug fix: Asynchronous processing time not reported correctly in Play 1.2.4
Bug fix: CXF transaction names not set to URI path if protocol is https

Java agent v2.9.0

Tue, 09 Oct 2012 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Support for Key Transactions. Key Transactions let you closely monitor these important key business transactions and receive alerts when they are performing poorly. For more information see the full documentation.
More metrics available in Custom Dashboards

Java agent v2.8.0

Tue, 11 Sep 2012 00:00:00 +0000

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Supports basic proxy authentication for the case where there is a proxy server between the agent and the internet. The configuration uses proxy_user and proxy_password settings.
To avoid reporting the same transaction trace repeatedly, the agent reports a number of the slowest transactions.
Bug fix: Transaction trace reported to wrong app if enable_auto_app_naming and browser requested a transaction trace

Java agent v3.0.1

Thu, 03 Oct 2013 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Fix: Issue at startup with JBoss and Glassfish

An issue in the 3.0.0 version caused startup of some versions of JBoss and Glassfish to fail. This version fixes that issue.
Fix: RUM not auto-instrumented for JSPs

The Java Agent should auto-instrument RUM header and footer in JSPs when using the Jasper engine. This did not work in 3.0.0. This version fixes that issue.

Java agent v3.0.0

Tue, 01 Oct 2013 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Spring AOP instrumentation

This version instruments any call that passes through an AOP pointcut that you have declared in your Spring application. This gives your additional insight into the call time of key Spring beans.
Performance Improvements

This version contains optimizations that reduce agent overhead.
Fixes: Hibernate improvements

In this version, we provide more consistent detail into Hibernate calls across supported version of Hibernate (3.3 - 4.2).
Fix: Removed need for WebSphere SSL work-around

Previous versions sometimes required a work-around when using WebSphere. This version removes the need for a work-around.
NOTE: Requires Java SE 6 or 7

Java Agent 3.0 requires Java SE 6 or 7. At signup or on the release notes page, you have the option to download a version of the agent that works with Java SE 5.

Java agent v3.1.0

Mon, 21 Oct 2013 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Percentiles and Histograms

The Java Agent now captures data that provides percentile and histogram views in the New Relic UI.
JAX-RS annotation instrumentation

The Java Agent now instruments and names web transactions based on javax.ws.rs annotations.
JAX-WS instrumentation

The Java Agent now instruments methods on classes that are marked with the javax.jws.WebService annotation.
Fix: In some cases, agent had excessive overhead on Spring AOP apps

The agent should now perform well for any Spring AOP application.
Fix: Play Framework instrumentation was ignoring the ignoreTransaction call

The Play Framework 2.x instrumentation now honors the New Relic API ignoreTransaction call.
Fix: Potential memory leak when app continually creates ClassLoaders

The Java Agent now handles applications where ClassLoaders are continuously created.
Fix: Agent zip distribution did not include the API source jar

The newrelic-api-sources.jar is now included in the zip file.

Java agent v3.10.0

Tue, 26 Aug 2014 00:00:00 +0000

Download this agent version

Improvements

Full support for Java SE 8

The New Relic Java agent now supports Java SE 8! Applications can now run on a Java 8 JVM, including those compiled to target Java 8 (i.e. -target 1.8). The system property newrelic.enable.java.8 is no longer necessary.
@RequestMapping annotation used to name web transactions

Where available, Spring Web Transactions are now named using the URI path pattern defined in the @RequestMapping annotation. This generally provides even more meaningful transaction names than controller methods. To disable this and revert back to naming using controllers, add this config to your newrelic.yml:
```
instrumentation:
    spring_annotations:
       enabled: false
```
WebSphere JMX metrics reported when global security is enabled

Prior to this version, JMX metrics could not be pulled by the agent with WebSphere when global security was enabled. This means custom JMX metrics in a yaml file and default JMX metrics displayed on the JVM Threads and Http Sessions tabs were not reported.
Servlet UserPrincipal name can be reported as an attribute

With this release, you can enable the capturing of the UserPrincipal name so that it is available in New Relic and as a transaction trace attribute. To enable:
```
class_transformer:
    com.newrelic.instrumentation.servlet-user:
      enabled: true
```
Non-Web Transactions can now be made Key Transactions with a custom apdex T

This feature will be available in the RPM UI very soon. It requires this or a higher version of the agent.

Fixes

Fix: Web transactions not always reported.

In some unusual cases the Agent stopped reporting web transactions. The agent would log an error that included the phrase "Inconsistent state"
Fix: WebSphere 7 reports active thread count on the JVM tab

The thread pool active count being displayed in the UI was actually the pool size.
Fix: Excess error reporting in Play apps

In Scala/Play apps, the agent was incorrectly logging errors when promises were resolved with a Failure.
Fix: Request headers are not read when cross application tracing is disabled

Disabling cross application tracing using these config settings did not stop the Agent from reading request headers.
```
cross_application_tracer:
enabled: false
```
Fix: NewRelic API methods prematurely deprecated

In 3.9.0, some API calls in com.newrelic.api.agent.NewRelic were prematurely deprecated. We are in the process of providing a more complete API for the New Relic agent. In an upcoming release, these methods may become deprecated, but with a stable and superior API alternative.

Java agent v3.1.1

Tue, 05 Nov 2013 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Fix: In some cases, metrics were not reported in Play 2 apps

The Java Agent now reports all metric data consistently.
Fix: The Java Agent was unable to instrument classes in WSO2 API Manager

The Java Agent now reports data for WSO2 applications.

Java agent v3.11.0

Tue, 30 Sep 2014 00:00:00 +0000

Download this agent version

Improvements

Spring Web Services
- The Java Agent now supports Spring Web Services. Transactions are named based on the SOAP method name. The agent also reports the SOAP version, content type, and SOAP Action.
Support for Auto-RUM and precompiled JSPs
- The Java agent now provides auto rum support when precompiling JSPs. To use auto rum when precompiling JSP files, add the agent as a java agent to your pre-compilation process.

Fixes

Fix: Under some circumstances the agent would report a LinkageError
Fix: Grails 2 transaction names had extra slash
Fix for auto-RUM
- In some cases when a script tag is before a head tag in a JSP file, the auto RUM instrumentation was failing to place the initial New Relic header script in the page.
Fix: Reduce overhead of Akka instrumentation when not used in conjunction with Play/Netty
Fix: RabbitMQ instrumentation reported unnecessary transactions
- basicPublish, basicGet, and nextDelivery no longer start short-lived transactions.

Java agent v3.12.0

Thu, 06 Nov 2014 00:00:00 +0000

Download this agent version

Fixes

Various bug fixes

Java agent v3.12.1

Mon, 22 Dec 2014 00:00:00 +0000

Download this agent version

Improvements

Play 2 async activity is no longer tracked when transaction is ignored.
Reduced GC overhead when monitoring Play 2 applications.
Reduced memory usage when inspecting slowest SQL statements.

Config Changes

stack_based_naming now false by default.

The stack_based_naming in the transaction_tracer section is now false by default. Stack-based naming caused significant overhead in many Scala applications, so it now must be set to true explicitly. Set to true for better naming of trace detail segments in Scala Play applications.
```
transaction_tracer:
    stack_based_naming: true
```

Fixes

Memory leak when applications using servlets are continuously reloaded inside the JVM.
Memory leak with long running transactions performing a high number of external calls.
In some cases for JBoss application servers, two JVMs were being displayed in the UI when there was actually only one.

Java agent v3.13.0

Tue, 20 Jan 2015 00:00:00 +0000

Download this agent version

Improvements:

Custom Insights events API

In addition to attaching custom attributes to the events that the Java agent generates automatically for each transaction, you can now record custom event types into Insights with the new NewRelic.getAgent().getInsights().recordCustomEvent API.
The agent now captures and reports thread profiles in XRay Sessions for non-web transactions.

Fixes:

Incorrect JMS transaction names for users of Oracle ATG Web Commerce
In rare cases, application code would encounter a NoClassDefFoundError for one or more classes contained in the newrelic.jar.

Java agent v3.14.0

Wed, 25 Feb 2015 00:00:00 +0000

Download this agent version

Improvements:

Synthetic transaction tracing

Synthetic monitors lets you monitor your site from around the world. When you use synthetic monitoring to monitor your Java application, up to 20 detailed transaction traces will now be captured every minute when the application is probed from synthetics. To learn more about this feature, visit our documentation
EJB Session Beans

The Java agent now monitors Enterprise Java Beans (EJB) 3.0 session beans. The agent instruments @Stateless and @Stateful EJBs, and those that extend java.ejb.SessionBean. The agent traces methods declared by corresponding interfaces annotated with @Remote and @Local.
Unified view for SQL database and NoSQL datastore products.

The response time charts in the application overview page will now include NoSQL datastores, such as Cassandra and MongoDB,and also the product name of existing SQL databases such as MySQL, Postgres, Oracle, etc. For existing SQL databases, in addition to the existing breakdown of SQL statements and operations, the queries are now also associated with the database product being used. For NoSQL datastores, such as Cassandra and MongoDB, we have now added information about operations performed against those products, similar to what is being done for SQL databases.

This new unified Databases page will enable the filtering of metrics and operations by product, and includes a table listing all operations.

Because this introduces a notable change to how SQL database metrics are collected, it is important that you upgrade the agent version on all hosts.If you are unable to transition to the latest agent version on all hosts at the same time, you can still access old and new metric data for SQL databases, but the information will be split across two separate views.
Datastax Cassandra client

Added support for the Datastax Cassandra client versions 2.1.2 or higher. This will include breakdowns in the overview chart, entries in the Databases tab, and segments in transaction traces. Note: uses of the client's async API will not be captured in transaction traces.
MongoDB client

Added support for MongoDB client versions 2.12.0 up to but not including 3.0+. This will include breakdowns in the overview chart, entries in the Databases tab, and segments in transaction traces.
API Reported Errors

API reported errors can now be prioritized on a transaction over tracer reported errors. Add the following config to allow prioritizing:
```
error_collector:
  ignoreErrorPriority: false
```

Fixes:

The Java Agent may now capture traces for transactions that resulted in an error (4xx or 5xx response code). Prior to this release, the agent would only capture traces for successful responses.
Updated default newrelic.yml to use transaction_events.max_samples_stored instead of deprecated analytics_events.max_samples_stored property.
JBoss dispatcher reports correctly for clustered environments where jboss.home and jboss.home.dir are not set.
Resolved a bug which caused certain Jetty configurations to stop sending metric data.
Under very light load, the Agent could send incorrect transaction timestamps.
Fixed parsing error in log_file_count setting. Prior to this release, this setting produced one more log file than expected.

Java agent v3.15.0

Tue, 31 Mar 2015 00:00:00 +0000

Download this agent version

Improvements:

Labels and Rollups

The New Relic Java agent now supports the ability to apply labels to applications, so that you can easily sort, filter, and page through all of the applications on your account's Applications list.

Configuration can be done in the newrelic.yml file:

labels: Server:One;Data Center:Primary

More information on using labels to categorize your applications can be found in the New Relic APM documentation.

With this version of the Java Agent, you can update Custom instrumentation XML in the extensions folder and it will be reloaded within a minute.

Fixes:

Prior to this version, some thread profiles would time out and not display. Thread profiles will now complete reliably.
The Java Agent now works around IBM JVM bug IV25688. The agent will scale back a small amount of its instrumentation on old IBM JVMs to avoid inducing the bug. The workaround should leave most customers unaffected. Loss of instrumentation caused by the workaround can be fixed by upgrading the JVM to the latest service release.

Java agent v3.16.1

Thu, 14 May 2015 00:00:00 +0000

Download this agent version

Improvements:

Redis

Added support for the Jedis client versions 1.4.0 or higher. You can now see your Redis calls in breakdowns in the overview chart, entries in the Databases tab, and segments in transaction traces.
RabbitMQ

Updated RabbitMQ instrumentation to support RabbitMQ 3.5 and higher.
Cross Application Tracing API

Use the cross application tracing API when the agent does not provide cross application tracing support for your application. See the documentation
Play 2 Framework

Improved instrumentation for Play controller classes.
Circuit Breaker

Starting in this release, the New Relic Java agent detects when memory is nearly exhausted and trips a “circuit breaker” that limits the agent’s memory usage. The agent won’t report transactions while the circuit breaker is tripped, so throughput will be understated. In the rare case that the circuit breaker trips, the New Relic UI will provide more information. For more details, see the documentation.
Added configuration to disable Deadlock Detection

Under very heavy load conditions with many threads, the Deadlock Detector service may slow response time. You can now disable this feature with the following setting:
```
deadlock_detector:
    enabled: false
```
Reduced the memory overhead of the Java agent

Fixes:

Play 2 Framework

The Java Agent now honors the segment_limit setting for async traces, and can now handle much deeper async traces. This is useful to decrease if you're experiencing slower response time or high memory overhead when executing large async transactions.

Cross-application requests from other New Relic-instrumented applications will reliably appear in the App and Transaction maps.
The proxy_host name is no longer sent to New Relic.
Fixed issue where external transactions were reported twice when using HttpURLConnection. Previously, this caused throughput to appear doubled.

Java agent v3.17.0

Thu, 11 Jun 2015 00:00:00 +0000

Download this agent version

Improvements

Websphere Liberty Profile

The Java agent now provides instrumentation for WebSphere Liberty Profile. This includes web transaction visibility, Cross Application Tracing, and app server stats.
Performance improvements

The Java agent now starts more quickly so applications are available sooner. This release also reduces agent overhead at run time.
Customize hostname displayed in APM

A new configuration setting has been added: process_host.display_name. When set in the newrelic.yml configuration file, the display name identifies the host in the APM UI, along with the hostname that the agent automatically captures.
```
process_host:
    display_name: hostname
```
In addition, the display name can be set using the NEW_RELIC_PROCESS_HOST_DISPLAY_NAME environment variable. This property can be viewed in all Insights transaction events.
WebLogic and WebSphere instance name available

The instance name for WebLogic and WebSphere application servers is now available in transaction traces, traced errors, and Insights transaction events.
Custom instrumentation of transaction attributes is disabled by default

Custom attributes defined using the Instrumentation tab in the UI are now disabled by default. In order to enable these attributes, you must have High-security mode disabled and you must place the following text in the common: block of your newrelic.yml:
```
reinstrument:
    attributes_enabled: true
```

Fixes

Very large thread profiles were failing to report to RPM, causing the site to display a time out message. The agent will now truncate the size of the profile before sending.
Cross application tracing date was failing to report when using Jersey 2 endpoints.
Spring AOP instrumentation is now disabled by default. It was exercising a bug in certain versions of Java 8 that caused the JVM to crash. To re-enable, include the following in your newrelic.yml:
```
com.newrelic.instrumentation.spring-aop-2:
       enabled: true
```
RabbitMQ metrics could double-report for some versions of RabbitMQ. This was introduced in Java agent version 3.16.1 and is fixed in this version.
In rare cases the agent would report a LinkageError.

Java agent v3.17.1

Tue, 30 Jun 2015 00:00:00 +0000

Download this agent version

Fixes

Fixed a bug in 3.17.0, that in rare cases could cause an application thread to die. In this case, the agent log has many messages, “ERROR: Inconsistent state!”

Java agent v3.18.0

Wed, 01 Jul 2015 00:00:00 +0000

Download this agent version

Improvements

Jetty

Updated Jetty instrumentation to support Jetty 9.3.
Thrift

Added support for Apache Thrift 0.8 and greater. This instrumentation automatically adds timing to Thrift calls and sets transaction names based on Thrift method names. It can be disabled in the newrelic.yml by adding:
```
com.newrelic.instrumentation.thrift-0.8:
    enabled: false
```
Resin

The New Relic Resin Instrumentation now reports errors as HttpErrors, allowing them to be ignored.
Heap Alerting

A new heap utilization metric has been created for alerting purposes. This metric tracks the percentage of heap in use as a number between 0 and 1, where 0 means no heap usage and 1 means a full heap. The new metric is: Memory/Heap/Utilization
Exception messages for allow list

Java exception messages will now be obfuscated when high-security mode is enabled. If specific exception messages should be allowed through, they can be added to your allow list with the following configuration property:
```
strip_exception_messages:
    whitelist: 'java.lang.NullPointerException,java.lang.IllegalStateException'
```
The allow list is a comma-delimited string of exception class package + class name. This can be enabled or disabled independently of high-security mode with the following property:
```
strip_exception_messages:
    enabled: true
```

Java agent v3.19.0

Wed, 29 Jul 2015 00:00:00 +0000

Download this agent version

Improvements

Redis

The agent’s Redis instrumentation is now more efficient.

Fixes

In some cases the HttpClient 3 instrumentation could overstate the external call count.
In rare cases the agent would report errors that it was configured to ignore.
Some line numbers did not display correctly in stack traces.

Java agent v3.19.1

Fri, 07 Aug 2015 00:00:00 +0000

Download this agent version

Fixes

In some cases JBoss 4.x could fail to start due to a NullPointerException.
In some cases Dropwizard appservers could fail to start due to a ClassCastException during log initialization.

Java agent v3.19.2

Thu, 13 Aug 2015 00:00:00 +0000

Download this agent version

Fixes

Fixed an issue that could cause NoClassDefFoundErrors when using JDBC ResultSet instrumentation on JBoss.

Java agent v3.2.0

Tue, 03 Dec 2013 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Glassfish 4 metrics for JVM Memory, Thread Pool, and Transactions

New Relic now displays JVM memory, thread pool, and transaction metrics for Glassfish 4. To expose these metrics, please set http-service, transaction- service, and web-container monitoring within Glassfish to high. To see the metrics in New Relic, go to Monitoring > JVMs.
Decreased agent overhead for Play 2

This version of the agent reduces the overhead that it incurs on Play 2. Play 2 users should upgrade for improved performance.

In addition to general overhead improvements, New Relic has introduced a new setting to reduce overhead even more for particularly low-latency applications. Note that this setting will make the call info in Trace Details more generic.
```
transaction_tracer:
  stack_based_naming: false
```
Manually disable auto RUM instrumentation for specific pages

For supported JSP engines, New Relic automatically adds RUM (Real User Monitoring) elements to the response HTML. If you like auto-RUM, but do not want to apply it to all pages, you can now disable it for select pages. The configuration property disabled_auto_pages in the browser_monitoring section can now be used to disable auto RUM instrumentation for a comma delimited list of pages. For example,
```
browser_monitoring:
  disabled_auto_pages: page1.jsp, page2.jsp
```
akka.actor.ActorKilledException is now ignored by default

The ActorKilledException is commonly thrown in Play applications as a control mechanism in normally functioning applications. In previous versions, this exception inflated the reported error rate. These exceptions are now ingored by default. You can override the default ignore_errors list to provide your own exceptions or to omit the ActorKilledException.
```
error_collector:
  ignore_errors: some.other.MyException
```
New Relic reports host capacity information

New Relic now reports physical CPU cores, logical CPU cores (hyperthreads), and physical memory. On non-Linux platforms, the agent runs a subprocess to retrieve this information. To see the info in New Relic, go to Settings > Environment > Environment Snapshot.
Report JVM name and revision to New Relic as part of JVM description

Recording the JVM name in addition to the vendor allows differentiation between different JVMs from the same vendor. To see these values in New Relic, go to Settings > Environment > Environment Snapshot and look for the "Java VM" and "Java VM Version" settings.
Fix: Support for Play 2.2

Web transactions were not being correctly captured under some circumstances for Play 2.2 applications. Web transactions are now correctly reported. Also note the change in command line syntax as of Play 2.2: https://docs.newrelic.com/docs/java/play-installation-for-java
Fix: Background tasks created by an @Trace annotation with a 'metricName' element did not show up in the New Relic UI.

Java agent v3.20.0

Tue, 01 Sep 2015 00:00:00 +0000

Download this agent version

Improvements:

JCache

The Java Agent now instruments the JCache API. The instrumentation times cache operations of implementations of the JCache API.

To get additional information about your operations in the Databases page, enable com.newrelic.instrumentation.jcache-datastore-1.0.0 in your newrelic.yml. This will incur additional overhead.
```
class_transformer:
   com.newrelic.instrumentation.jcache-datastore-1.0.0:
     enabled: true
```

Fixes:

Circuit Breaker alerts now better align with data displayed in JVMs tab.
In some cases the Java Agent's HttpURLConnection instrumentation could report incorrect external response time metrics
The Java Agent's MongoDB instrumentation no longer reports errors due to runtime exceptions that are caught and handled by applications.
Fixed an issue where Guice dynamic proxies could be instrumented, potentially causing MGI issues.
In rare cases a deadlock would occur at startup on some WebSphere applications.
Fixed an issue that could cause missing Cross Application Tracing information on WebLogic 12 when using HttpURLConnection.

Java agent v3.21.0

Thu, 01 Oct 2015 00:00:00 +0000

Download this agent version

Improvements

Advanced Analytics for APM Errors

With this release, the agent reports TransactionError events. These new events power the beta feature Advanced Analytics for APM Errors (apply here
to participate). The error events are also available today through New Relic Insights
.

Advanced Analytics for APM Errors lets you see all of your errors, with granular detail. Filter and group by any attribute to analyze them. Take action to resolve issues through collaboration.

Fixes

Fixed a memory leak in async continuations instrumentation for Jetty 7 and 8.
Improved error handling with invalid JMX .yml extension files.
Improved Circuit Breaker logging in the event of a Circuit Breaker trip.
Fixed a bug in Tomcat 7+ instrumentation where request parameters could occasionally get stripped when using an async servlet with capture_params set to true.

Notes

The Java Agent now collects the following information for web transactions:

Accept, Host, User-Agent, Content-Length HTTP request headers
HTTP request method, for example POST or GET
Content-Type HTTP response header

Known issues

Fixed in 3.25.0:
- Setting enable_custom_tracing configuration flag to false can inadvertently disable Netty instrumentation.
- In some cases JAX-RS annotations on interfaces are not observed, causing transactions using JAX-RS services to be named on the servlet rather than the web servicepath and method.
Fixed in 3.24.1:
- The Java agent's Play 2 transaction tracing instrumentation may be incomplete and cause gaps in cross application tracing.
Fixed in 3.24.0:
- The Java agent's EJB instrumentation may cause a StackOverflowException to appear in application logs.
- Applications may continue to experience the additional Circuit Breaker overhead even when disabled.
- The Java agent may experience increased overhead when using Cross Application Tracing and a large number of threads.
Fixed in 3.23.0
- This release may experience a memory leak within the agent for Tomcat containing a large number of static JSPs (5000+).
- When a transaction makes multiple calls to a database with the same obfuscated SQL, a NullPointerException is may get thrown in the agent.
- This release contains a bug in New Relic's Cross Application Tracing (CAT) that can cause incorrect service and transaction maps.

The problem happens when non-identical applications, with identical transaction names, would appear to be communicating (in the Transaction / Service maps), when in fact, they were not.

Using a combination of pre-3.23.0 and 3.23.0+ can result in external calls between the old and new agents to not show up in the map. To fix this, upgrade all of your agents to 3.23.0+ at the same time.

Java agent v3.2.1

Fri, 06 Dec 2013 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Fix: Exceptions thrown from conflicting JAXB versions

The New Relic Java agent now supports customers using any JAXB or Xerces version. This bug was introduced in version 3.1.0.
Fix: Usage of the newrelic.bootstrap_classpath system property

In version 3.2.0, the newrelic.bootstrap_classpath system property caused an IllegalAccessError. That bug has been fixed. Note also that this system property has been deprecated and should not be used.
Fix: Data collection for customers using the IBM JVM without WebSphere

New Relic now supports customers using an IBM JVM without running WebSphere. In this scenario, you must set the sync_startup flag set to true in the common section of their newrelic.yml.
```
sync_startup: true
```

Java agent v3.22.0

Fri, 06 Nov 2015 00:00:00 +0000

Download this agent version

Improvements

Play Framework 2.4 Instrumentation, and Play Framework 2 Improvements

Previous Java Agent releases supported the Play Framework up to version 2.3. This release includes instrumentation for Play 2.4.x. This release provides more insight than ever before for all versions of Play 2, including improved segment names, and better signal-to-noise ratio in transaction details.

This instrumentation also takes advantage of the new response time line in the New Relic UI. Because Play is a reactive framework that encourages concurrent activity, your total time for transaction components will often be greater than the response time. If the total time is less than response time, it may indicate resource exhaustion. By separating the total time from the response time, you get a clear picture of when you are getting the benefit of concurrency.

If you have used the Java Agent to monitor Play before this release, you may see a decrease in response time. The new response time metric more accurately reflects the time from initial request to response.

We support Play applications written in Java or Scala 2.9.3 - 2.11.x.

Note: The deprecated -Dnewrelic.bootstrap_classpath system property can result in missing instrumentation and should not be used.
Netty 3.4 - 4.x Instrumentation

This release updates our Netty support to include versions from 3.4 to 4.x. Previous release supported up to Netty 3.9. The agent will start transactions for server inbound I/O. The agent will instrument Netty HTTP methods to enable cross application tracing (CAT) in Netty transactions.
AsyncHttpClient Instrumentation 1.0.2 - 1.9.x

In this release, you will see the time spent in external service calls made using AsyncHttpClient (also known as Ning Http Client). If the external service is also running New Relic, you will see cross application tracing (CAT) details as well. This includes external calls made from Play WSAPI, which uses AsyncHttpClient.

Note: As in previous releases, Play 1 applications will not report AsyncHttpClient activity.
Akka Instrumentation 2.0 - 2.4

This release enhances our Akka instrumentation by linking an actor message sender to an actor message receiver in the same transaction. In order to avoid over-instrumentation, our Akka instrumentation does not actually start transactions. If you would like a given actor call to mark the beginning of a transaction, you will need to use the @Trace(dispatcher=true) annotation, or some other form of custom instrumentation.

Notes:

This release supports core Akka, not all Akka extensions. In particular, it does not identify transactions that have been routed by Spray, Akka HTTP, or Akka Streams. We have heard from customers that these frameworks are important, and we expect to support them soon! Stay tuned to the Java agent incubator, since we may provide an early access instrumentation module for these frameworks before we release them in the agent.

Known Issues:

If your application uses AsyncHttpClient's WebSockets, do not use this version. AsyncHttpClient WebSockets requests will fail, or the application will not start.
In some cases, calls to NewRelic's getBrowserTimingHeader and getBrowserTimingFooter are ignored.

Java agent v3.2.2

Thu, 12 Dec 2013 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Fix: Play 2.2 instrumentation in action methods

In version 3.2.0 and 3.2.1, the Java agent failed to instrument calls present in a controller's action method. This means database calls, external calls, and custom instrumented calls within the action method were not being reported to New Relic. This bug has been fixed.
Fix: Invalid exclusive time errors with Play 2.2

In version 3.2.0 and 3.2.1, the Java agent sometimes reported error messages to the newrelic log indicating an "Invalid exclusive time". This error has been fixed.
Fix: Inaccurate async wait time with Play 2.x

In version 3.2.0 and 3.2.1, the Java agent reported an async wait time for Play 2.x transactions that was too large. This bug has been fixed.

Java agent v3.22.1

Mon, 16 Nov 2015 00:00:00 +0000

Download this agent version

Fixes

Fixed an issue that caused Ning's AsyncHttpClient WebSockets requests to fail, or the application not to start.
Fixed an issue that could cause an extra transaction to be created, a background transaction named NettyDispatcher.
Removed the deprecated bootstrap.classpath configuration, as it could result in the Java agent's instrumentation failing to load.

Java agent v3.2.3

Mon, 16 Dec 2013 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Fix: JBoss 7 fails to start with Java 1.6

Starting with version 3.2.0 of the Java agent, JBoss 7 application servers fail to start when running Java 1.6. An IllegalStateException is printed to System.out. This bug has been fixed.

Java agent v3.23.0

Tue, 01 Dec 2015 00:00:00 +0000

Download this agent version

Improvements

Hystrix instrumentation

This release contains support for versions 1.0.2 through 1.4 of the Hystrix framework. You will now see timing information related to each Hystrix Command's run and getFallback methods. Chained Hystrix commands will be linked into one transaction.

Fixes

This release fixes a bug in New Relic's Cross Application Tracing (CAT) that could cause incorrect service and transaction maps.

The problem would happen when non-identical applications, with identical transaction names, would appear to be communicating (in the Transaction / Service maps), when in fact, they were not.

Note: Using a combination of pre-3.23.0 and 3.23.0+ can result in external calls between the old and new agents to not show up in the map. To fix this, upgrade all of your agents to 3.23.0+ at the same time
Resolved an issue where an application running on Tomcat and containing a large number of static JSPs (5000+) could cause a memory leak within the agent.

Java agent v3.24.0

Tue, 15 Dec 2015 00:00:00 +0000

Download this agent version

Improvements:

MongoDB

The Java agent now reports synchronous calls to the Mongo Java Driver 2.12 through 3.1. You will see the Mongo operations in breakdowns in the Applications Overview chart, entries in the Databases tab, and segments in transaction traces. Note: The asynchronous driver is not supported.
Akka HTTP and Spray

The Java agent now reports and names transactions received through Akka HTTP 1.0, Akka HTTP 2.0 and Spray. Transactions are named intuitively based on route DSLs. This instrumentation also supports Cross Application Tracing from calling systems. With our previously released support for Akka, your Akka HTTP and Spray applications will now include activity of those transactions all the way through your actor systems.

Fixes:

In rare cases the Java agent's EJB instrumentation could cause a StackOverflowException to appear in application logs.
In some cases the Java agent's Netty instrumentation could throw a NullPointerException to application code.
Improve performance when using Cross Application Tracing and a large number of threads.
In some cases the transaction would not be reported when using Akka with mutable messages.

Known Issues:

Play 2.x requests will produce empty responses when the circuit breaker is tripped. We recommend Play 2.x users disable the circuit breaker when using Java agent versions 3.22 or higher.

Java agent v3.24.1

Mon, 21 Dec 2015 00:00:00 +0000

Download this agent version

Fixes

Fixed an issue that caused Play 2.x requests to produce empty responses when the circuit breaker is tripped.

Java agent v3.25.0

Mon, 18 Jan 2016 00:00:00 +0000

Download this agent version

Improvements

Performance improvements

The Java agent now starts up to 50% faster. Your applications will be available that much sooner.

Fixes

In some cases JAX-RS annotations on interfaces were not being observed, causing transactions using JAX-RS services to be named on the servlet rather than the web servicepath and method.
Fixed an issue that prevents Spray and Akka-HTTP instrumentation from applying when using Scala 2.10.
Fixed an issue that caused Play 2.x requests to produce empty responses when the circuit breaker is tripped.
Fixed an issue where setting enable_custom_tracing to false could inadvertently disable Netty instrumentation.

Known Issues

Fixed in 3.29.0
- Applications that use Play and Ning AsyncHttpClient may miss transactions.
- The thread profiler may not report data while profiling certain Scala classes.
Fixed in 3.28.0
- Fixed a bug that could cause Akka Http instrumentation to throw a NullPointerException into customer code.
Fixed in 3.27.0
- Fixed an issue where the agent treated HTTP headers as being case sensitive, causing CAT to miss under certain conditions.
- Fixed various issues related to the proper handling of multibyte character encoding.
Fixed in 3.26.x
- CXF instrumentation can name transactions based on auto-generated proxy classes. Later agents now normalizes CXF transaction names.
- EJB instrumentation may cause a NullPointerException in application code, and erroneously set transaction names. In later versions, the agent records a metric.
- The Cross Application Tracing API caused Application Response time to be attributed to other transaction time, and prevented linking of transaction traces when doing CAT.
- Request queuing calculations could show queuing time as a steadily increasing value instead of the correct time.
- HttpURLConnection External metrics may not report on the IBM J9 JVM.
- Transaction traces may report external segments for non I/O calls in Apache HttpClient.
- The Java agent will now read Cross Application Tracing HTTP header names regardless of case.
- Fixed a bug that could cause cross application tracing between the New Relic Java agent and non-Java New Relic agents to fail.

Java agent v3.26.1

Thu, 25 Feb 2016 00:00:00 +0000

Download this agent version

Improvements

PostgreSQL

This release adds improved support for PostgreSQL 8.0+ with jdbc3+. All of these versions now include support for explain plans.

Java agent v3.26.0

Tue, 23 Feb 2016 00:00:00 +0000

Download this agent version

Improvements

Spray Client

The agent now identifies external calls when Spray Client is used. You will see your Spray Client calls with the hostname and port of the destination. The calls also have support for Cross Application Tracing, and are shown in Service Maps and Transaction Maps.
The agent now tracks Futures started in Spray routes.
The agent now identifies transactions when spray-can is used without spray-routing.
Slick

The agent now tracks async activity created by Typesafe/Lightbend's functional-relational-mapper, Slick. If the underlying database driver is supported by the agent the database activity will be traced.
Improvements for JDBC

The Java agent’s JDBC instrumentation now provides more consistent and complete data for supported JDBC drivers. The Java agent supports the following drivers:
- MySQL 5.1.4 - 5.1.x
- PostgreSQL 8.2-504 - 9.4-1206 (jdbc4 and jdbc41 drivers only)
- Oracle ojdbc14, ojdbc5, ojdbc6, ojdbc7
- Microsoft SQLServer 2.0 - 4.2
- jTDS 1.2 - 1.3.x
- DB2 9.1 - 10.x
- Derby 10.6.1.0 - 10.x
- H2 1.0.x - 1.4.x
- HSQL 1.7.2.2 - 2.x
- MariaDB 1.1.7 - 1.3.x
Note Previous versions of the Java Agent had partial “generic” support for other JDBC drivers. The new, improved JDBC instrumentation replaces the “generic” JDBC instrumentation.

Fixes

Fixed a bug where CXF would name transactions based on auto-generated proxy classes. The agent now normalizes CXF transaction names.
Fixed a bug in EJB instrumentation that could cause a NullPointerException in application code.
Fixed a bug where the EJB instrumentation erroneously set transaction names. In this version, the agent records a metric.
Fixed a bug in the Cross Application Tracing API that caused Application Response time to be attributed to other transaction time, and prevented linking of transaction traces when doing CAT.
Fixed a bug in request queueing calculations where queueing time could show up as a steadily increasing value instead of the correct time.
Fixed a bug that prevented HttpURLConnection External metrics from reporting on the IBM J9 JVM.
With Spray routing, fixed a bug that incorrectly set the transaction name of similar route names or set them to "Unknown Route".
Fixed a bug where some transaction traces would report external segments for non I/O calls in Apache HttpClient.
The Java Agent will now read Cross Application Tracing HTTP header names regardless of case.
Fixed a bug that could cause cross application tracing between the New Relic Java Agent and non-Java New Relic Agents to fail.

Known Issues

Postgres JDBC

This release does not contain support for some versions of the PostgreSQL jdbc3 drivers supported in previous releases. We recommend that you use 3.26.1.

Java agent v3.27.0

Wed, 30 Mar 2016 00:00:00 +0000

Download this agent version

Improvements

Spymemcached

The Java agent now provides visibility into your applications’ usage of Memcached when using the Spymemcached client versions 2.11 to 2.12. You will see the calls in the application breakdown, in trace details, on the Databases page, in Transaction maps, and in Service maps.
JDBC Drivers

This release adds support for the following JDBC drivers:
- INet Oracle Driver (Oranxo) 3.14
- Sybase (jConnect) JDBC 3 driver

Fixes

Fixed an issue where the agent treated HTTP headers as being case sensitive, causing CAT to miss under certain conditions.
Fixed an issue where error data could be dropped, causing 413 status code errors to be reported in the agent log.
Fixed a bug in spray-http and akka-http routing libraries where response times and/or route names could be reported incorrectly when using Futures within the route.
Fixed various issues related to the proper handling of multibyte character encoding.
Fixed a bug in Java agent version 3.26.x that could cause the Thread Profiler to time out.
Fixed a bug where an error could get printed to the agent log when making SQL queries from an asynchronous framework.

Notes

In support of an upcoming feature, the Java agent is now capable of reporting class metadata including class method signatures, method annotations, class annotations, field annotations, field types, and field names.

This reporting is on by default and can be explicitly disabled in the agent by setting the property in your newrelic.yml configuration file:

command_parser:
    blacklist: send_module_metadata

Java agent v3.29.0

Tue, 24 May 2016 00:00:00 +0000

Download this agent version

Improvements

JDBC instrumentation
- JDBC ResultSet instrumentation performance has been improved.
- Instrumentation has been added for:
- i-Net Merlia 7.0.3 database driver
- Generic JDBC drivers
Cassandra

This release adds instrumentation for the Cassandra Datastax 3.0 Driver including slow query support. You’ll see relevant breakdowns in the overview chart, entries in the Databases tab, and segments in transaction traces.

Note: Uses of the client's async API are not currently supported.

Fixes:

Fixed a bug which caused some applications that use Play and Ning AsyncHttpClient to miss transactions.
Fixed an issue which would cause the thread profiler to not report data while profiling some Scala classes.
Fixed a rare bug where a RuntimeException is thrown during class transformation which can prevent some instrumentation from being applied.
Fixes a rare case where Tomcat ClassLoaders could leak memory when using a JDBC driver bundled in your application after reloading a web application.

Java agent v3.28.0

Wed, 20 Apr 2016 00:00:00 +0000

Download this agent version

Improvements

Cassandra

This release adds slow query tracking to Cassandra queries made via the Datastax driver. You’ll now see slow CQL queries on the Databases page and within Transaction Traces. You must add the following to your newrelic.yml configuration to enable this feature in High-security mode:
```
transaction_tracer:
      slow_query_whitelist: 
       'com.newrelic.instrumentation.cassandra-datastax-2.1.2'
```
MongoDB

The Java agent now reports synchronous calls made via MongoDB Java driver 2.14. You will see MongoDB represented on the Overview page, on the Databases page, and in Transaction traces. Note: The asynchronous driver is not yet supported.
Apache Tomcat

This release adds support for Tomcat 8.5
Akka
- This release adds support for Akka forwarding and Akka broadcasting. The agent will now trace messages broadcast or forwarded to actors.
- When the system sends a message to an Actor, the agent now reports the name of the actor system that sent the message. Previously, the agent reported “deadletters” under these circumstances.
Async performance

This release adds performance enhancements for asynchronous frameworks, especially Hystrix. Performance in Hystrix will noticeably improve for most applications, and will be up to 3x faster when tracing low-latency requests (response time <3ms). Performance for low-latency Play applications will be up to 30% faster.
JDBC

This release adds support for the following JDBC drivers:
- MySQL 6.0.2 and higher
- i-Net Oranxo 3.06
- i-Net MERLIA 8.04.03 and 8.06

Fixes

Fixed a bug that could cause Akka Http instrumentation to throw a NullPointerException into customer code.
Fixed a bug in the Spymemcached instrumentation that would report operations with the name “None” instead of the correct operation name.
Fixed a bug that could cause highly asynchronous applications to experience a memory leak in the NewRelic TransactionService.

Java agent v3.30.0

Tue, 28 Jun 2016 00:00:00 +0000

Download this agent version

Improvements

Mule ESB 3.4 - 3.6

This release adds instrumentation for Mulesoft Mule ESB Server versions 3.4 through 3.6. Requests to an HTTP Transport will show in New Relic as web transactions. Mule ESB Server instances will appear as "dispatchers" on the overview page and the JVM metrics page. All of the usual features of New Relic APM are supported including alerting, error reporting, JMS puts and takes, cross application tracing, transaction traces, key transactions, external services, and database call reporting.

NOTE: The newer HTTP operation-based Connector is not yet supported.
Play 2.5

This release adds instrumentation for the Play 2.5 framework. The previous Java Agent release supports versions of Play up to 2.4.
Cassandra async 2.1.2+ and 3.x

This release adds instrumentation for asynchronous queries in versions 2.1.2+ and 3.x of the Datastax Cassandra driver, including slow query support. You’ll see relevant breakdowns in the overview chart, entries on the Databases page, and segments in transaction traces.
Async Http Client 2.x

This release adds instrumentation for external service calls made using Async Http Client versions 2.x. If the called external service is also running New Relic, you will see cross application tracing details as well. This instrumentation will also capture external calls made from Play WSAPI (which uses Async Http Client).
Transaction traces for key transactions

If you set an Apdex value for a key transaction, the agent will now capture transaction traces based on that key transaction's Apdex value if it's smaller than the application’s Apdex value.
JDBC performance and overhead improved

This release offers better performance and lower overhead of JDBC instrumentation, especially in situations with large numbers of connections.

Fixes:

Fixed multiple issues related to Java Agent logging including:
- ClassCastExceptions thrown into customer application logs
- Agent logging being diverted into customer application logs
Fixed a bug where transactions could timeout during agent harvest, resulting in missing metrics and logging: "Traced activity timed out after 600 seconds. The traced_activity_timeout configuration parameter can be used to adjust this timeout.”
Resolved Metric grouping issue in Spray/Akka tell instrumentation. The agent now names temporary actors "temp".
In rare cases a ClassCircularityError could be induced by the agent when running with a custom security manager.
Fixed issue where a database connection can get labeled as "JDBC" instead of the more specific, supported database type such as "MySQL" or "PostgreSQL". This issue specifically affects customers running with a proxying or delegating JDBC connection.

Java agent v3.30.1

Wed, 20 Jul 2016 00:00:00 +0000

Download this agent version

Fixes

Fixed a security issue that could send external HTTP request parameters to New Relic via transaction traces for applications that do all of the following:

Use Java agent 3.6.0 or higher*
Use Apache HttpClient 4.0 or higher
Haven’t disabled transaction_traces

*For Java agent versions 3.6.0-3.25.0, this issue only affects cross-application traces.

Recommended for applications that may include sensitive information in external service call request parameters.

If you can’t upgrade the agent immediately, there are a few workarounds:

Disable transaction traces
Disable only cross-application tracing. This resolves the issue with Java agents prior to 3.26.0.

You can also delete existing transaction traces.

Java agent v3.3.1

Tue, 07 Jan 2014 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

JMS Messaging

New Relic now gives you insight into the performance of your JMS message processing, both incoming and outgoing messages.

New Relic now shows transactions initiated via JMS 1.1 message receipt. These transactions show up in the New Relic UI as background tasks of type "Message". In addition, JMS 1.1 message creation is shown in transaction traces.
Grails 1.3.7 to 2.3.x

New Relic now provides first-class visibility into your Grails applications. Grails web transactions are now named based on the Grails controller. The transactions track the details of your calls to JDBC, Hibernate, and other important frameworks, and provides full access to the New Relic Java agent API from Groovy. Grails installation instructions can be found here
Updated instrumentation for supported app servers

New Relic has updated the instrumentation of the application servers we support. In the process, we have updated the list of app servers that we instrument. For a current list of supported app server versions, see https://docs.newrelic.com/docs/java/new-relic-for-java
Fix: New Relic did not instrument Apache HttpClient 4.3

Previous versions of the agent did not instrument HttpClient 4.3.x. That version is now properly supported.
Fix: Java Agent failed on Weblogic with a certicate exception

In some cases running Weblogic, the Java Agent would fail certificate validation when connecting to New Relic. That bug has been fixed.
Fix: Java Agent suppressed application logging

In version 3.2.3, the Java agent sometimes suppressed application logging. That bug has been fixed in this version.
Fix: Java Agent was logging error messages regarding "weaved classes"

In version 3.2, the Java agent wrote innocuous error messages to its log similar to the following:

ERROR: javax/servlet/ServletOutputStream is marked as a weaved class, but no methods are matched to be weaved.

That bug has been fixed in this version.
Fix: Text instructions in the sample newrelic.yml file were improved

If you are upgrading from a previous version of the agent, consider applying your configuration to this new version of the yml file.

Java agent v3.31.0

Wed, 03 Aug 2016 00:00:00 +0000

Download this agent version

Improvements

Mule ESB 3.6-3.8 including the new HTTP Connector

This release adds instrumentation for Mulesoft Mule ESB Server versions 3.6-3.8, including the new HTTP Connector made available in Mule 3.6. This release continues to support the old HTTP Transport. Mule ESB Server instances will appear as "dispatchers" on the overview page and the JVM metrics page. Requests to an HTTP (operation-based) Connector will show in New Relic as web transactions. All of the usual features of New Relic APM are supported including alerting, error reporting, JMS puts and takes, cross application tracing, transaction traces, key transactions, external services, and database call reporting.
OkHttp client 3.0-3.4

This release adds instrumentation for OkHttp client for versions 3.0-3.4. Both synchronous and asynchronous calls are supported, as well as the usual features for HTTP clients in New Relic APM such as cross application tracing and the external services page.
Akka HTTP 2.4.5

The Java agent now reports and names transactions received through Akka HTTP 2.4.5, in addition to previously available Akka HTTP support.
Spring transaction naming

The java agent now supports naming transactions based on the path element of Spring RequestMapping annotation.

Fixes

Fixed an issue that was preventing Jetty JMX threads metrics from being pulled in later versions of Jetty 9.X.
Fixed bug in the recordMetric API that in rare cases could start an unwanted long running transaction.
Fixed a memory leak in the Async Servlet instrumentation.
Fixed a bug in the setRequestAndResponse API that could throw a java.lang.NumberFormatException in the customer’s application when the circuit breaker trips.

Java agent v3.31.1

Wed, 10 Aug 2016 00:00:00 +0000

Download this agent version

Fixes

Fixed a bug that caused a StackOverflow exception for drivers that execute a query on Connection.getMetaData().

Note: This issue was introduced in Java agent version 3.30.0.

Java agent v3.3.2

Fri, 10 Jan 2014 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Fix: Duplicate annotation exception

In some rare cases involving generated a proxy class, the application may encounter an exception

AnnotationFormatError: Duplicate annotation for class

That bug has been fixed in this version.
Fix: VerifyError

In certain cases such as the Wildfly app server, the application may encounter a VerifyError. That bug has been fixed in this version.

Java agent v3.32.0

Mon, 19 Sep 2016 00:00:00 +0000

Download this agent version

Improvements

WebLogic

This release adds official support for WebLogic versions 12.2.x
Performance Improvements

Improvements in Java agent startup time, particularly on modular ClassLoader architectures (such as JBoss)

Fixes:

Fixed bug in spymemcached instrumentation that would incorrectly name segments in transaction traces that contained “get-and-touch” operations.
Improved Play 2.5 instrumentation
- Fixed memory leak for large POST requests.
- Fixed incorrect response times. Previously, large uploads could cause inflated response times.
- The agent now tracks PlayRequestHandler and no longer shows the short-lived NettyDispatcher transactions.
Fixed a bug that could cause cross application tracing to display URLs as “Unknown” in transaction traces when the URL did not include the port number.
Fixed a bug in Jetty 9.3 instrumentation where transactions were not reported and memory was leaked if an incoming async request was wrapped by a framework or Jetty itself.

Java agent v3.33.0

Wed, 02 Nov 2016 00:00:00 +0000

Download this agent version

Improvements

Database instance reporting

The agent now reports database instance information for most supported databases. With the additional database instance information, transaction traces and slow query traces will provide the database server and database name for the queries displayed. You will see instance-level information when connecting by using the following drivers:
- Any JDBC driver, including those in our compatibility doc.
- DataStax Cassandra driver (2.1.2, 3.0 to 3.1).
- Jedis Redis driver (1.4 to 2.9).
- Mongo (2.12.0 to 2.13.3, 3.1 to 3.3).
- Spymemcached (2.11 to 2.12). Note that instance-level information is not reported for calls to the getBulk API method..

Bug fixes

Fixed a bug in Play 2.5 instrumentation that could cause the agent to report shorter response times when using Action.async.
SQL stored procedure names are now reported in more edge cases such as “exec @param = stored_procedure”
Fixed an issue where explain plans were not being executed for versions 9.0-9.3 of PostgreSQL.
Fixed an issue where the agent could cause a Mule application request to fail with a NotSerializableException reported in the application log.
Fixed an issue where JVM versions that do not support ThreadCpuTime() would throw an UnsupportedOperationException, preventing the JVM from starting.
Fixed a potential memory leak in versions of Jetty 7 and 8 when using CometD.
Fixed an issue where the Hystrix toObservable method was double counting metrics on newer versions of Java 7 and all versions of Java 8.

Java agent v3.34.0

Wed, 14 Dec 2016 00:00:00 +0000

Download this agent version

Improvements

Solr

The agent now reports database instance information for Solr. With the additional database instance information, transaction traces and slow query traces will provide the database server and database name for the queries displayed.
IBM JDK 8 Support

The newest versions of WebSphere Application Server and WebSphere Liberty Profile ship with the IBM JDK 8. This release is compatible with IBM JDK 8.

Fixes

Fixed an issue in which asynchronous instrumentation could interact with instrumentation for JDBC ResultSet or a limited set of other frameworks, leading to loss of transaction reporting.
Fixed an issue in which transactions that executed the Spring Framework error handler could be given a generic name. These transactions will now retain their previously-assigned name.
Fixed a bug introduced in 3.33.0 where use of the X-Ray sessions feature could cause the Agent to stop reporting transactions.
Fixed a bug in the agent that prevented Error Events from linking to corresponding Traced Errors when created outside of a transaction
Fixes a Tomcat-specific issue where Transactions would incorrectly report extremely long response times in the ServletRequestListener.requestInitialized() method.
Improved metric grouping issues in several frameworks including Akka tell calls.
Fixed bug in noticeError API. The agent now includes custom attributes in errors when the API is called outside a Transaction.
Fixed an issue where custom XML instrumentation could cause a null pointer exception in application code when custom attributes are set for a method that passes a null parameter.
Fixed an issue in the Agent API method recordCustomEvent() that could cause loss of custom events created using this API. Customer who do not use the recordCustomEvent() API are not affected. Previously, unexpected argument types could result in the loss of both the event and additional custom events recorded in the same 1-minute period. As a result of this fix, users of the recordCustomEvent API may discover that events that have never been visible in the Insights API become visible.

Known issues

Fixed in 3.35.2
- Applications that use the Spray Client instrumentation may throw a NullPointerException into customer logs
- Applications that use the Netty instrumentation may get a StackOverflowException when calling ServerBootstrap.bind() many times
- Oracle WebLogic Server 12.2 applications will not display WebLogic specific JMX metrics
- SQL parsing may throw a StackOverflowError and prevent large database statements from being sent up to New Relic
Fixed in 3.36.0
- Queue Time may be misreported on the Overview page for applications injecting the X-Queue-Start or X-Request-Start HTTP headers
- Applications that have custom Hystrix Commands that are subclassed multiple times in Groovy can cause an application to throw an exception on startup
Fixed in 3.37.0
- Solr: Applications that use Solr and have reported to New Relic APM previously with an agent version prior to 3.34.0 will not display the Solr page

Java agent v3.35.0

Wed, 11 Jan 2017 00:00:00 +0000

Improvements

Known Issue

Several customers have reported an issue with this release in which the app fails with a ClassFormatError. For this reason, this release is not recommended and has been removed from New Relic's download site. Please use release 3.34.0 instead.

We keep the note here because the 3.35.0 is still available on the Maven Central Repository.

We will release a fix for the issue as soon as possible.

Changes

JAX-RS/Jersey 2

This agent release officially adds support for JAX-RS 1.1-2.0.

The release instruments the @Suspend annotation when using the Jersey 2 implementation of JAX-RS.
OkHttp 3.5

This release updates our instrumentation to cover OkHttp 3.5.

Fixes

Fixes an edge case in Spray Client instrumentation where a NullPointerException was being thrown into customer logs
Fixes a potential StackOverflowException from Netty instrumentation when calling ServerBootstrap.bind() many times
Fixes a bug that prevented display of JMX metrics for Oracle WebLogic Server 12.2
Fixes issue where SQL parsing would throw a StackOverflowError and prevent large database statements from being sent up to New Relic
Improve performance of complex SQL statement parsing in the agent, reducing overhead for apps that make many SQL calls

Java agent v3.35.1

Thu, 12 Jan 2017 00:00:00 +0000

Download this agent version

Known Issue

This release contains a bug that could cause the app to fail with a VerifyError. Please use version 3.34.0 instead.

We will release a fix for the issue when we have thoroughly tested the fix for edge cases.

Fixes

Fixes an issue where an application can fail to start with a ClassFormatError when using Spring, Jersey, or any JAX-RS framework with Java Agent v3.35.0.

Java agent v3.35.2

Tue, 17 Jan 2017 00:00:00 +0000

Download this agent version

Note

If you are using Spring AOP, Jersey, or any JAX-RS framework, use this 3.35.2 release rather than 3.35.0 or 3.35.1.

Fixes

Fixes an issue where an application can fail to start with a: java.lang.VerifyError: Bad local variable type error when using Spring AOP, Jersey, or any JAX-RS framework with Java Agent 3.35.0 or 3.35.1.

Java agent v3.36.0

Wed, 15 Feb 2017 00:00:00 +0000

Download this agent version

Improvements

APIs

This release adds a number of APIs that will allow you to instrument and get expanded visibility into frameworks, libraries, and any custom code that New Relic does not automatically instrument. In addition to instrumenting your web frameworks, you can also instrument calls to and from messaging systems, database calls, and external calls! By passing context about your code to the APIs, you will get the same reporting, including cross application tracing, that you get with New Relic’s built-in instrumentation.
Solr

This release adds support for Solr versions 5 and 6 (up to and including version 6.3.0).

Fixes

Fixes a bug that prevents an application from starting up when a JAX-RS annotated method contains more than 8 parameters.
Fixes an issue that affected Spring and JAX-RS applications compiled with the Java 8 flag javac -parameters. The issue would cause the application to throw a java.lang.reflect.MalformedParametersException exception.
Fixes bug that affected applications implementing JAX-RS endpoints using static methods.
The agent now reports WildFly dispatcher name and version.
Fixes a bug in which Queue Time could be misreported on the Overview page for customers injecting the X-Queue-Start or X-Request-Start HTTP headers. This fix brings the Java Agent into compliance with the behavior of other New Relic Agents.
Fixes an issue in which custom Hystrix Commands that are subclassed multiple times in Groovy cause an application to throw an exception on startup.

Java agent v3.38.0

Mon, 24 Apr 2017 00:00:00 +0000

Download this agent version

Improvements

Expected Errors This release provides you with several flexible error configuration options to control how your errors are reported. With this addition, you can now configure certain exceptions that you expect your application logic will throw. These “expected errors” will not be counted towards your application error rate and Apdex; you will only be alerted on errors that truly affect the health of your application. Expected errors can be configured by exception class or HTTP response code. When specifying an exception class, you can provide an error message to match. See the documentation for details.
Custom CA Bundle

A path to a custom SSL certificate bundle can now be specified in the agent configuration by using the following top level configuration:
```
ca_bundle_path: /path/to/ca/cert/bundle.pem
```

Fixes

Fixed a bug where applications running on Tomcat could see duplicated or misnamed transactions for async endpoints.
Fixed a bug that caused transactions to report with an inflated apdex. The affected transactions had to meet the following conditions:
- A status code >= 400
- No error set on the transaction
- markResponseSent() or addOutboundHeaders() was not called from the API In this case, the agent will now consider that transaction call to be frustrating for the purposes of calculating apdex.
Fixed a bug where the loaded class count on the JVM tab is reported as a much larger value than the actual number of loaded classes. In certain circumstances this bug can cause memory and CPU over-utilization.
Fixed a bug where response times in ServletRequestListener.requestInitialized() would incorrectly appear much larger than the actual values when using JBoss.

Java agent v3.37.0

Wed, 29 Mar 2017 00:00:00 +0000

Download this agent version

Improvements

Async APIs
This release adds new APIs for instrumenting asynchronous work. If your transactions have asynchronous work (such as database queries or external calls) that is not automatically monitored by the Java Agent, you can use the APIs to link that work to your transactions. For more information, see the documentation.
OkHttp 3.6
This release adds support for OkHttp 3.6.x. You will now see OkHttp 3.6 calls as external calls in New Relic.

Fixes

Fixes an issue where applications running on Tomcat 8.5 could see duplicated or misnamed Transactions for async endpoints.
Fixes an edge case issue where users of Spring AOP can get an UndeclaredThrowableException when using the Java Agent.
Fixes root and current working directory jars not showing up in the UI.
Fixes an issue which prevented the Solr updates and Solr caches tabs from displaying in the New Relic UI for applications that are reporting Solr data for the first time.

Java agent v3.39.0

Tue, 23 May 2017 00:00:00 +0000

Download this agent version

Bug fixes

Fixed an issue in which setting "agent_enabled" to false in newrelic.yml caused an IncompatibleClassChangeError in the application on startup. The agent can now be disabled without side-effect.
Fixed an issue where the agent throws an exception if null keys or values are passed to the recordCustomEvent() API. The agent now ignores these null values.
Fixed a rare issue where the agent throws a NullPointerException in the application during JDBC calls. The agent now reports these calls but may report an “Unknown” database.
Fixed an issue where a VerifyError is thrown in the application code when using Spring or JAX-RS annotations on a Kotlin method with a default parameter.
Fixed an issue where external HTTP metrics could be reported outside of a transaction when using HttpURLConnection. The agent now ignores these calls.

Java agent v3.39.1

Tue, 30 May 2017 00:00:00 +0000

Download this agent version

Fixes:

Fixed an issue in which the agent could in rare cases send a raw SQL query as a transaction attribute when an error was thrown

Java agent v3.4.0

Thu, 16 Jan 2014 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Fix: Java agent should honor enable_auto_app_naming

Starting with Java agent 3.3.1, the enable_auto_app_naming flag was being ignored. This bug has been fixed.
Fix: Setting configuration properties in newrelic.yml configuration file.

Starting with version 3.0, some properties such as max_stack_trace_lines could not be set in the newrelic.yml configuration property. This bug has been fixed.
Fix: Java agent should honor JAX-RS annotations with New Relic annotations

New Relic's Java agent should handle methods that contain a New Relic annotation along with a JAX-RS annotation correctly. Previously the New Relic annotation was being ignored.
Fix: Play transaction does not complete until timeout expires

New Relic's Java agent now handles firstCompletedOf to Futures correctly.
Additional functionality to API call addCustomParameter

New Relic's API call addCustomParameter will now add the custom parameters to New Relic. For more information, see http://newrelic.com/software-analytics

Java agent v3.40.0

Mon, 26 Jun 2017 00:00:00 +0000

Download this agent version

Improvements

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.

Java agent v3.4.1

Tue, 21 Jan 2014 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

Fix: In some cases, Play 2.2 didn't report transactions

When a chain of promises resolved, specifically using Future.flatMap(), lingering promises prevented the transaction from completing, in which case the transaction wouldn't be reported for the app. This is now tracked correctly.
Fix: Improved performance when instrumented code is not running in a transaction

Avoids unnecessary work when code instrumented by the Java agent is not running in the scope of a transaction.

Java agent v3.41.0

Tue, 25 Jul 2017 00:00:00 +0000

Download this agent version

Improvements

Vert.x

The Java agent now provides visibility into your applications built using the Vert.x toolkit (supported versions 3.3.0 through 3.4.2). The agent instruments Vert.x Web, Vert.x Core, and Vert.x HTTP client. With this instrumentation, the agent will identify and name your transactions based on Vert.x web routing paths. The agent will also time web handlers, track async handlers, and external calls made with Vert.x HTTP client.
Slick

With this release, the Java agent now supports Slick 3.2
API

Added ExtendedRequest API class to report content-length for HTTP responses. See Transaction.setWebResponse API for more details.

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.

Java agent v3.4.2

Thu, 23 Jan 2014 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End of life policy.

Notes

Fix: Solr caches and Solr updates data not appearing

Starting with version 3.4.1, Solr caches and updates were not appearing in the UI. This bug has been fixed.
Fix: JVM tab thread pool, session, and transaction data not appearing

Starting with version 3.4.1, some data was not appearing under the JVM tab. This bug has been fixed.

Java agent v3.42.0

Mon, 28 Aug 2017 00:00:00 +0000

Download this agent version

Improvements

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.

Java agent v3.43.0

Wed, 27 Sep 2017 00:00:00 +0000

Download this agent version

Improvements

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

Java agent v3.44.1

Tue, 07 Nov 2017 00:00:00 +0000

Download this agent version

Note

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.

Java agent v3.45.0

Mon, 11 Dec 2017 00:00:00 +0000

Download this agent version

Improvements

RabbitMQ

The agent now provides instrumentation for RabbitMQ 5.0.

Note:

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:
```
message_tracer:
    segment_parameters:
      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.

Java agent v3.46.0

Mon, 08 Jan 2018 00:00:00 +0000

Download this agent version

Improvements

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.

Java agent v3.47.0

Mon, 05 Feb 2018 00:00:00 +0000

Download this agent version

Improvements

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

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.

Java agent v3.48.0

Mon, 12 Mar 2018 00:00:00 +0000

Download this agent version

Improvements

Customers using Tomcat, WebSphere Liberty, or Resin now have data source information available. Data source information includes the number of active and idle connections, as well as the maximum possible connections. This information can be seen under the Data Source tab on the JVMs page
CompletableFuture instrumentation is more efficient
Disabling SSL connections to New Relic has been deprecated. SSL connections are enabled by default. In a future release, the option to disable SSL will be removed.

Bug fixes

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

Java agent v3.5.0

Wed, 05 Mar 2014 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End-of-life policy.

Notes

New Relic supports WildFly 8.0

The Java Agent now provides instrumentation for WildFly 8.0. You will see the same great visibility into your web transactions, app server stats, and frameworks that you have with previous versions of JBoss.
Fix: PostgreSQL explain plan bug

Fixes PostgreSQL bug that allowed parameters to be sent in explain plans under some circumstances. Parameters are now masked prior to sending when explain plans are enabled (explain_enabled: true) and record_sql is set to 'obfuscated'.
Fix: SQL parameter obfuscation didn't work if the parameter value contained a newline

The record_sql: obfuscated config setting did not properly mask parameters when it included a newline character. This bug has been fixed.
Agent no longer supports obfuscation of individual fields

Previous versions of the agent allowed an obfuscatedsql_fields option to select specific field names to obfuscate when record_sql: raw. We have discovered rare cases in which this feature would not mask SQL parameters correctly, so we have removed the configuration option. Now, if obfuscated_sql_fields is set, the setting of record_sql: raw is ignored and _all fields are masked.
Fix: In some cases, an agent could fail to reconnect to New Relic

Fixed several issues that in rare cases could cause the agent to cease reporting data until JVM restart.
Fix: Transaction name specified in XML configuration was being ignored

In some cases transaction names set in XML files in the extensions folder were being ignored. This bug has been fixed in this release.
Fix: Jetty 9.1 transactions were not showing up in 3.3.x or higher agents

Starting with the 3.3.1 agent, customers were not seeing transactions from Jetty 9.1. This bug has been fixed.
Fix: Websphere 7.0 was not being instrumented

Starting in agent version 3.3.0, WebSphere 7.0 was not being instrumented. This bug has been fixed.
Fix: Solr tabs in UI not always appearing

If you are running a Solr application and not seeing any tabs, please update to this version.

Java agent v3.47.1

Wed, 07 Mar 2018 00:00:00 +0000

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.

Java agent v3.5.1

Thu, 27 Mar 2014 00:00:00 +0000

Download this agent version

The end-of-life date for this agent version is July 29, 2019. To update to the latest agent version, see Update the agent. For more information, see End of life policy.

Notes

Fix: Auto-RUM bug

Starting in version 3.5.0 of the Java agent, in rare cases Auto-RUM could cause the New Relic header to be placed within a script tag. This bug has been fixed.
Fix: In rare cases, agent stops reporting

In rare cases, the Java Agent hung on socketRead while performing an SSL handshake and would not report data until JVM restart. This bug has been fixed.
Fix: Occasionally missed web transaction when using ResultSet

In version 3.5.0 of the agent some transactions that use a JDBC ResultSet were missing in the UI. The agent log would show an "Inconsistent State" error. This bug has been fixed.
Fix: X-Ray Sessions bugs.

X-Ray Sessions sometimes returned no transaction traces. A memory leak with X-Ray Sessions when many sessions were run was also fixed.

Java agent v3.7.0

Tue, 20 May 2014 00:00:00 +0000

Download this agent version

Notes

Flexible capturing of attributes

The Java agent offers the ability to fine tune the attributes being sent to New Relic. Please see our docs site for more information on configuring attributes: https://docs.newrelic.com/docs/java/java-agent-attributes
Agent-Side High Security Configuration

If your account is set to high security in the New Relic UI, you must add the following to your local newrelic.yml configuration file:
```
high_security: true
```
Without this property, the agent will stop collecting data when high security is enabled in the New Relic UI. See https://docs.newrelic.com/docs/subscriptions/high-security
Discovery of hostname reported to New Relic

If New Relic reports an IP address for your hostname, you can now control whether the host name is an IP version 4 or 6 address by setting the following property in your newrelic.yml configuration file:
```
process_host: 
  ipv_preference: {4 or 6}
```
Improved JMX metric naming

You can now set the metric name when configuring JMX metrics through a custom yaml file using the property "root_metric_name". Note, all of the JMX metrics will still be prefixed with "JMX" and end with the name of the attribute. See https://docs.newrelic.com/docs/java/custom-jmx-yaml-examples
Fix: Naming of CGLib classes

CGLib auto generated classes with Spring resulted in poor metric names. The agent now excludes the random part from the name.
Fix: JMS transaction naming

JMS onMessage instrumentation now uses a lower priority for naming transactions and honors the enable_auto_transaction_naming config.
Improved Jetty coverage

Jetty versions 9.04 through 9.06 were not instrumented. This has been fixed.
Fix: Potential memory leak from database calls

In some cases when database work is performed outside of a New Relic transaction, a memory leak could occur. This bug has been present in the agent since 3.5.0.
Fix: VerifyError can occur when using Nevado JMS.

Java agent v3.6.0

Thu, 24 Apr 2014 00:00:00 +0000

Download this agent version

Notes

Enhanced XML for custom instrumentation

The custom XML xsd has been enhanced to support the instrumentation of interfaces, subclasses, and method annotations. These enhancements give you much more flexibility to identify transactions and add monitoring of components without changes to your source code.
Fix: Agent could cause VerifyError

In specific cases, the agent could cause verification errors.
Fix: Embedded Jetty instrumentation

Starting with the 3.3.1 agent, transactions were not reported for some configurations of embedded Jetty.
Fix: Exceptions incorrectly reported

In some cases exceptions were reported even if configured to be ignored.
Fix: Embedded Tomcat not reporting JMX Builtin metrics

In newer versions of embedded Tomcat the agent wasn't collecting JMX metrics properly.
Fix: Apache HttpClient 4.3 not consistently reported

The Java agent now instruments Apache HttpClient 4.3 calls, including the new call patterns introduced in 4.3.
Fix: RESTEasy transactions

In certain instances, transactions between applications were not getting linked correctly when RESTEasy was used.
Fix: JBoss 7 port not reported correctly

The port was not reported correctly for some JBoss users.
Fix: Auto-RUM bug

Starting in version 3.5.0 of the Java agent, in rare cases Auto-RUM could cause the New Relic footer script to be placed within a script tag.
Fix: Errors not reporting with some versions WebSphere 7.0

In some Fix Packs of WebSphere 7.0, the agent did not report errors properly.
Fix: Agent works properly inside a folder with + in the path

The Java agent did not initialize properly when in a folder with a + character in the pathname.
Fix: Agent HttpClient logging

The Agent's HttpClient was writing to the app server's log when it discovered a log4j appender.
Fix: Inconsistent State with Play 1.2.x

In some cases the agent was logging an "Inconsistent state!" message and not reporting a transaction.
Fix: Invalid errors for Stripes

The Agent was erroneously reporting spurious 404 errors for web apps using Stripes.
Fix: Hanging threads in the Agent with SQL Prepared Statements

Under rare circumstances, threads could hang in the Agent when an application with multiple threads made heavy use of SQL Prepared Statements.
Fix: Request queue time was incorrect for some versions of nginx

Nginx fractional second header values for queue and server start times are now parsed correctly.
Fix: XML entity expansion with non-SSL connection to New Relic

Fixed an XML entity expansion vulnerability that only occurs when the agent is configured with ssl: false; the default is true. The agent already has other protection against unauthorized entity expansion. This fix is an additional layer of protection.
Fix: In rare case, agent can cause application thread to hang

Under rare circumstances, an application thread could hang when an application with multiple threads made heavy use of SQL Prepared Statements.

Java agent v3.7.1

Tue, 03 Jun 2014 00:00:00 +0000

Download this agent version

Notes

Fix: NewRelic.setRequestAndResponse API call was not backward-compatible

Implementation classes of the com.newrelic.api.agent.Request and com.newrelic.api.agent.Response interfaces compiled with a pre-3.5.0 version of newrelic-api.jar threw a java.lang.AbstractMethodError when used with a 3.5.0 or higher version of the Agent.
Fix: NewRelic.setRequestAndResponse can cause LinkageError

For some app servers, calling NewRelic.setRequestAndResponse API caused a java.lang.LinkageError: loader constraint violation
Fix: ignoreTransaction attribute ignored

The ignoreTransaction="true" attribute in custom xml had no effect. The transaction was not ignored even with "true" set.
Fix: In rare cases, Auto-RUM failed to add the New Relic header script to JSP pages.
Fix: Naming of CGLib classes

Improved the fix in 3.7.0 for excluding the random part from the name of CGLib generated class.
Fix: Agent works properly inside a folder with + in the path

Improved the fix in 3.7.0 for a directory path with a + character.

Java agent v3.7.2

Wed, 11 Jun 2014 00:00:00 +0000

Download this agent version

Notes

Support for Play 2.3

The Java Agent now provides full support for Play 2.3. In particular, transaction naming is based on the controller action.

Java agent v3.8.0

Mon, 30 Jun 2014 00:00:00 +0000

Download this agent version

Notes

Experimental support for Java SE 8

This version includes experimental support for Java 8. Code that is known to work with Java SE 8 and compiled for Java 6 or 7 (such as Tomcat 8, Play Framework 2.3, etc) should work fine. We would like your feedback if you run into any trouble running code compiled for Java SE 8.

Please only try this in non-production environments. We are eager for your feedback as we work to make Java 8 support production-ready. To enable Java SE 8 compatibility, set the following system property on your system:

-Dnewrelic.enable.java.8
Support for Hibernate 4.3

The Java agent now reports details on calls to Hibernate 4.3 as well as previous versions.
Fix: Cross-Application Tracing didn't trace when caller used WLS 11g and SOAP.

In Oracle WebLogic Server 11g, cross-application tracing (CAT) failed for external calls originating in the default SOAP pipeline, producing an exception in the log. This bug has been fixed.
Fix: Old DocumentationBuilderFactory can cause agent to disable itself

When using a DocumentBuilderFactory implementation compiled with Java 1.4 or below an abstract method error was being thrown, causing the agent to disable itself.
Fix: Agent not detecting async servlets in WebSphere 8.x

The Java Agent was not detecting the call to AsyncContext.complete(), so it was not reporting async servlet calls.

Java agent v3.8.1

Thu, 10 Jul 2014 00:00:00 +0000

Download this agent version

Notes

Fix: EJB application transaction metrics reporting correctly for WebLogic

In version 3.8.0 of the agent, EJB application transaction metrics for WebLogic were reporting the data as the average value per a bean instead of the total value per an application. This has been fixed and the data can now be found under the JVM tab.
Fix: App Map incomplete

If a web request made an external call to another app, the app making the web request did not appear in the App Map. Moreover, subsequent external calls to other apps did not appear in the App Map either.

Java agent v3.8.2

Mon, 28 Jul 2014 00:00:00 +0000

Download this agent version

Fixed: Instrumentation missing including browser monitoring

There was a bug in the agent that caused several instrumentation modules to not be loaded. This bug occurred when no extensions directory existed or the extensions directory was empty. This fix will allow auto-RUM to report normally. This bug was introduced in 3.8.0.
Fix: Missing metrics with Java 2 Security

When Java 2 Security was enabled, the agent failed to report some metrics. This bug was introduced in 3.8.0.
Fix: Agent could stop reporting transactions

For Jetty applications, the agent could stop reporting transactions if an uncaught exception was thrown. This bug was introduced in 3.6.0.
Fix: Agent not reporting external services in Play 2.3

The Java Agent was not reporting calls to external services.

Java agent v3.9.0

Thu, 31 Jul 2014 00:00:00 +0000

Download this agent version

New Features

Support for new Cross Application Trace map

This release enhances cross application tracing with the new trace map visualization of your app's cross application calls. The new visualization helps you spot bottlenecks in external services within transaction traces and gives you an end-to-end understanding of how the transaction trace is used by other applications and services. This leads to faster problem diagnosis and better collaboration across teams. All agents involved in the cross application communication must be upgraded to see the complete graph. You can view cross application traces in the transaction trace drill-down.
Support for RabbitMQ

You can now see messages sent to and received from RabbitMQ 2.7.0 or higher. The time spent processing a dequeued message is shown as a Message transaction.
Support for SOAP over CXF

In this release, we provide automated instrumentation of your SOAP calls when using CXF 2.7.

Improvements

Absolute maximum for max_samples_stored lifted

In previous versions of the agent, max_samples_stored could not be set to more than 10000. This restriction has been lifted, which can help avoid sampling.

Fixes

Enable Cross Application Tracing for all valid uses of HttpURLConnection

Prior to this, certain uses of HttpURLConnection between two New Relic apps would fail to be recognized as Cross Application Traces and instead show up as external calls.
Allow customers to set the system property logback.ContextSelector

Prior to this fix, the agent would throw a ClassNotFoundException when the system property logback.ContextSelector was set.
Wrong Application name in App Map when Auto App Naming is enabled

When the enable_auto_app_naming config setting is set to true, the auto-named apps are incorrectly identified as the default app in the App Map.

Java agent v4.0.0

Wed, 04 Apr 2018 00:00:00 +0000

Download this agent version

Improvements

Removed the SSL configuration option: SSL is now always used in communication with New Relic servers. The newrelic.yml ssl configuration and -Dnewrelic.config.ssl system property are no longer used. Setting either value to anything other than true will result in logging a warning.
Minimum version required for use in EU data center.

Fixes

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

Java agent v4.0.1

Thu, 19 Apr 2018 00:00:00 +0000

Download this agent version

Fixes

Fixes an issue Introduced in 3.48.0 with event sampling. The agent would only report the first max_samples_stored events in a given minute reporting period and disregard the remainder for that minute. With the fix, the agent randomly samples those events across the reporting period.

Java agent v4.1.0

Wed, 02 May 2018 00:00:00 +0000

Download this agent version

Improvements

Configuration for custom_insights_events.max_samples_stored format in YAML has been changed. For agents 4.1.0 and above, the old .yml config setting will be ignored, which will result in the agent defaulting to max samples stored of 10,000 custom events. When you update your agent, please migrate to the new format:

custom_insights_events:
    enabled: true
    max_samples_stored: 5000

The agent will log a warning message when it detects that the java.endorsed.dirs property is used. Classes in these directories cannot be instrumented by the agent because they are loaded by the bootstrap classloader.

Fixes

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.
Addresses cases where the agent could not parse database statements that included the IGNORE and INTO keywords.

Java agent v4.10.0

Wed, 23 Jan 2019 00:00:00 +0000

Download this agent version

Improvements

This release adds Transaction event attributes that provide context between your Kubernetes cluster and services. For details on the benefits (public beta coming soon) see this blog post.
The Java agent now supports setting all configuration options via Environment variables. Environment variables will take precedence over newrelic.yml but cannot be updated dynamically since they are read statically on application startup.
Adds instrumentation for the Akka HTTP client, versions 10.0 to 10.1.x. This client is used via the Http().singleRequest() method and the agent will now automatically capture these requests as External metrics.
Support for MySQL connector 8.0.x
Adds official support for Akka Http 10.1.6
Span event attributes can now be filtered using include / exclude rules.

span_events:
    enabled: true
    attributes:
      include:
      exclude:

Rename transaction trace segment parameter key from uri to http.url and rename trace key from database_name to db.instance.

Fixes

Fixes an issue where Akka HTTP instrumentation can cause higher than normal memory usage when an async Directive is used in the route for an Akka HTTP based app. This can also result in mis-named transactions for any paths underneath the custom Directive.

Java agent v4.11.0

Tue, 12 Feb 2019 00:00:00 +0000

Download this agent version

Improvements:

Vert.x 3.6

The Java agent now provides visibility into your applications built using the Vert.x 3.6. The agent instruments Vert.x Web, Vert.x Core, and Vert.x HTTP client. With this instrumentation, the agent will identify and name your transactions based on Vert.x web routing paths. The agent will also time web handlers, track async handlers, and external calls made with Vert.x HTTP client.
Wildfly 12-15

The agent now supports Wildfly versions 12 through 15.

Fixes:

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

Known Issues

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.

Fixes in 5.0.0

The agent no longer requires a newrelic.yml even when the 'app_name' and 'license_key' configuration options are set via environment variables and/or system properties. For more details, see [Java agent configuration(]https://docs.newrelic.com/docs/agents/java-agent/configuration/java-agen...).
HttpSessions JMX metrics were not reporting for Websphere Liberty Profile applications.
The transaction_events.max_samples_stored configuration value in the newrelic.yml would incorrectly override the system properties or environment variable values
Applications running on Wildfly 12 - 15 would fail start with NoClassDefFound errors for Java agent classes.
Play applications where external calls inside of future callbacks using async-http-client would not be recorded.
Setting log_limit_in_kbytes would result in the agent not logging to the agent log file if log_file_count was also set to less than 2.
Webflux status codes which were not recognized by Spring Webflux caused a 500 status code to be returned and an exception in application logs.

Fixes in 5.1.0

Fixed an issue in the Scala instrumentation that would cause an Java.lang.IllegalArgumentException: to be thrown when the Lightbend Cinnamon agent is in use.
Fixed issue where cross application tracing headers were incorrectly parsed when distributed tracing is enabled. Applications that use both distributed tracing and cross application tracing will no longer report external transaction breakdown metrics.
Fixed an issue where the agent’s Kafka instrumentation would report WakeupExceptions as errors in New Relic. These exceptions will no longer be reported.
Fixed a Log4J ClassCastException for applications running on the IBM J9 JVM that set a custom logging manager via the -Djava.util.logging.manager system parameter.
The agent now supports using the thread profiler when the send_environment_info configuration is disabled.

Fixes in 5.2.0

Fixed an issue where very long-running transactions with a large number of segments would cause an excessive amount of memory usage. The agent will no longer trace segments once the segment_limit has been reached.

Fixes in 5.3.0

Akka-http instrumentation would name transactions incorrectly when using an asynchronous onComplete callback to match routes.
The agent’s JaxRS instrumentation did not apply to cases where a concrete class implements the same method from two different interfaces.
The agent would not report JMX metrics when one or more composite attributes were null.
Akka-http path matching instrumentation could produce NullPointerExceptions when using a "repeat" path segment with no values. Transactions that pass some values will report as-is, but transactions that pass no values will be reported with a different segment in the metric name: "().repeat()".
The ignore_status_codes system property was not getting applied correctly.

Fixes in 5.4.0

Transaction traces would occasionally miss segments when using the spring @Async annotation with servlets.
Jax-RS instrumentation was not starting transactions.
A potential race condition during agent startup that would manifest as a NoClassDefFoundError for internal New Relic classes.
Akka-http instrumentation would attempt multiple retransforms of the same class.
The noticeError API would drop custom attributes that weren't of type String, Number, or Boolean, such as Enums or other custom types.

Fixes in 5.6.0

Spring Webflux WebClient would not track external calls when constructed with baseUrl(String baseUrl).
The NewRelic.getAgent().getConfig().getValue() api would not check configuration values set via environment variables.
The agent’s completable-future instrumentation could hold a reference to Tokens after they were expired, which could cause excessive memory usage.
Error traces could report to the wrong application when auto_app_naming is enabled and there were errors from two different application names getting reported during the same harvest.
The agent’s MongoDB instrumentation would instrument the same builder used by the async and reactive-streams drivers, resulting in excessive memory usage and incorrect transaction times. Note: The agent will no longer instrument the sync MongoDB driver if the async and/or reactive-streams drivers are on the application’s classpath.

Fixes in 5.7.0

Calls to NewRelic.getAgent().getTracedMethod().addOutboundRequestHeaders() will no longer throw an exception if a traced method has started but a transaction has not. This could happen by calling this in a method annotated with @Trace(async=true) before a token is linked.
Updates Guava to the newest release.
NoClassDefFoundError would occur in agent logs when a spring controller is used without a root level RequestMapping annotation.
The gc_time metric, which was enabled by default in version 5.2.0, has now been disabled by default since its results are often misleading.

Fixes in 5.8.0

The Solr 7 instrumentation would not report Update JMX metrics.
HttpURLConnection instrumentation produced External metrics only when network methods (getInputStream, getResponseCode) are called.
MongoDB instrumentation would report duplicate metrics when applications invoked MongoClientOptions.build() more than once.

Fixes in 5.9.0

The ca_bundle_path configuration setting would fail to correctly import certificates when running on IBM J9
Clarified the startup log message about the state of browser monitoring for the current application.
The agent logger would sometimes throw a NullPointerException
The agent would stop reporting Kafka metrics when one or more clients where closed
HttpURLConnection instrumentation could cause a NullPointerException in the agent logs and fail to report External metrics

Fixes in 5.10.0

In an effort to modernize our language and improve clarity, we have renamed several configuration values. The old names will still work for now, but they will all be removed in the next major version.

transaction_tracer.slow_query_whitelist is now transaction_tracer.collect_slow_queries_from

strip_exception_messages.whitelist is now strip_exception_messages.allowed_classes

command_parser.blacklist is now command_parser.disallow
The strip_exception_messages config now excludes nested exception messages
The agent will now use a lightweight tracer for SQL tracers beyond the segment_limit, improving performance in cases with a high number of segments.
The agent would fail to report the Docker containerId for some combinations of systemd and Kubernetes
The agent logger would fail to log with: “ERROR RollingFileAppender 'File': No TriggeringPolicy provided” when newrelic.config.log_file_count>1 and newrelic.config.isDaily=false and newrelic.config.log_limit_bytes=0

Java agent v4.12.0

Wed, 20 Mar 2019 00:00:00 +0000

Download this agent version

Improvements

Kafka-clients

The Java agent now supports the kafka-clients library. The agent will automatically report up Kafka metrics to New Relic.

Optional support is provided for reporting Kafka metrics as Insights events and for enabling distributed tracing. More information can be found in the New Relic documentation.
Java 12, Coretto and Zulu

The New Relic Java agent is now fully compatible with Java 12. This release also adds support for the Amazon Coretto and Azul Zulu JDKs.

New APIs

Added ignoreErrors() to the Transaction API, allowing all errors reported within a specific transaction to be ignored.
Added addCustomParameters(Map<String, Object>) API, allowing multiple custom parameters to be added to a transaction at once.
Updated the noticeError() API documentation to clarify that when the api is invoked multiple times while in a transaction, only the first error will be reported.

Deprecated APIs

The custom transport channel API is now deprecated in favor of the Distributed Tracing API.
The skipTransactionTrace attribute on the @Trace annotation is now deprecated. The excludeFromTransactionTrace attribute should be used in its place.

Deprecated Instrumentation

JetS3t

Removed built-in instrumentation for JetS3t. The agent will continue to report external calls made with the JetS3t client.

Fixes

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

Java agent v4.12.1

Wed, 27 Mar 2019 00:00:00 +0000

Download this agent version

Fixes

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.

Java agent v4.3.0

Tue, 31 Jul 2018 00:00:00 +0000

Download this agent version

Improvements

Distributed tracing

Distributed tracing lets you see the path that a request takes as it travels through your distributed system. By showing the distributed activity through a unified view, you can troubleshoot and understand a complex system better than ever before.

Distributed tracing is available with an APM Pro or equivalent subscription. To see a complete distributed trace, you need to enable the feature on a set of neighboring services. Enabling distributed tracing changes the behavior of some New Relic features, so carefully consult the transition guide before you enable this feature.

To enable distributed tracing, set enabled to true in the distributed_tracing section in the newrelic.yml config file.

distributed_tracing:
    enabled: true

Added configuration option proxy_scheme to allow the agent to connect via https only proxies.

Fixes

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

Java agent v4.2.0

Tue, 12 Jun 2018 00:00:00 +0000

Download this agent version

Bug fixes

Fixed a bug where transactions were being kept alive for too long when application is under heavy GC, causing inaccurate throughput to be reported.
Fixed 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.
Fixed 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.
Fixed a bug where Jersey Client and HttpUrlConnection could be double instrumented, resulting in inflated external call count.
Fixed a bug where the total time and response time for a long running task could be misreported.

Java agent v4.5.0

Tue, 04 Sep 2018 00:00:00 +0000

Download this agent version

Improvements

Apache HttpAsyncClient

The Java agent now provides instrumentation for Apache HttpAsyncClient 4.1+. You will see your HttpAsyncClient calls as externals in New Relic.
AsyncHttpClient

The Java agent now provides instrumentation for AsyncHttpClient. You will now see the time spent in external service calls made using AsyncHttpClient in New Relic. If the external service is also running New Relic, you will see cross application tracing (CAT) details as well.
Vert.x 3.5

The Java agent now provides visibility into your applications built using the Vert.x 3.5. The agent instruments Vert.x Web, Vert.x Core, and Vert.x HTTP client. With this instrumentation, the agent will identify and name your transactions based on Vert.x web routing paths. The agent will also time web handlers, track async handlers, and external calls made with Vert.x HTTP client.
JBoss EAP 7

The Java Agent now provides instrumentation for JBoss EAP 7. You will now see the same visibility into your web transactions, app server stats, and frameworks that you have with previous versions of JBoss EAP.
Play 2.7

The Java Agent now provides instrumentation for Play 2.7. The previous Java agent release supports versions of Play up to 2.6.
WebSphere Liberty

Added ThreadPool metrics for WebSphere Liberty Profile. You will now see the active threads in the Threads tab of the JVM metrics page

Fixes

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.

Java agent v4.4.0

Wed, 08 Aug 2018 00:00:00 +0000

Download this agent version

Improvements

Java 10

The New Relic Java agent is now fully compatible with Java 10. For more on JDK release and the Java agent, see this topic on the Explorers Hub.

Not compatible with Java 6

In order to continue to innovate and efficiently provide new capabilities to our customers who run on the JVM, this and future agent versions are not compatible with Java 6. If you are running Java 6, you may continue to use Java agent 4.3.0 or lower. For details, see this topic on the Explorers Hub.

Akka 2.5 and Akka HTTP 10.1

The Java agent now supports Akka 2.5.x and Akka HTTP 10.1.x. You will see your Akka HTTP calls as New Relic transactions, see the hand-offs between Akka actors, and understand the calls to other databases and services.

Solr 7

The Java agent now supports Solr 7.x. New Relic’s Solr support reports database calls to Solr servers as well as monitors the Solr server itself.

Known Issue: JMX stats collection for Solr 7 isn't supported as of this release.

WebLogic datasource

The Java agent now displays health data about WebLogic’s datasource in the Datasource tab under the JVM page.

Fixes

Fixed 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.
Fixed 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.
Fixed 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.
Fixed 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.

Java agent v4.6.0

Mon, 24 Sep 2018 00:00:00 +0000

Download this agent version

Improvements

Spring 5

The Java Agent now provides instrumentation for Spring 5 and Webflux. The agent will name transactions based on router functions as well as Spring controller and spring web annotations. The agent also provides support for Spring WebClient to capture external requests and timing.

Spring 5 instrumentation works with Spring Boot, Tomcat, and Jetty.

Note if you have previously disabled Spring instrumentation: There is a new spring-4.3.0 instrumentation module that gets used in place of the previous spring-4.2.0 module for any customers running Spring 4.3.0 and above. If you had previously disabled support for spring-4.2.0 and you are running spring-4.3.0 you will want to change your class_transformer section in your newrelic.yml from:
```
class_transformer:
  com.newrelic.instrumentation.spring-4.2.0:
    enabled: false
```
to:
```
class_transformer:
  com.newrelic.instrumentation.spring-4.3.0:
    enabled: false
```

Fixes

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.

Known Issues

Transaction reporting to New Relic may be delayed by up to 10 minutes when Spring WebClient is used to create http requests that never execute.

Java agent v4.7.0

Wed, 03 Oct 2018 00:00:00 +0000

Download this agent version

Improvements

Java 11

The New Relic Java agent is now fully compatible with Java 11. For more on JDK releases and the Java agent, see this topic on the Explorers Hub.

Solr 7.0 JMX Metrics

The Java agent now collects JMX metrics for Solr 7.0

Java agent v4.9.0

Tue, 18 Dec 2018 00:00:00 +0000

Download this agent version

Improvements

The 'request.uri' attribute is now included in Transaction events and corresponding Transaction Error events. As a result this attribute can now be queried in New Relic. It may be excluded via the exclude list in the attributes section of the yaml config file. It is also excluded when High-security mode is enabled.
Distributed Tracing can now be enabled at the same time as auto app naming. Each application created by this setting will share an event reservoir for Distributed Tracing.
Updates Akka HTTP instrumentation to support the newest version of Akka HTTP, 10.1.5 and above.

Fixes

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.

Java agent v4.8.0

Tue, 13 Nov 2018 00:00:00 +0000

Download this agent version

Fixes

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.

Java agent v5.0.0

Wed, 24 Apr 2019 00:00:00 +0000

Download this agent version

Improvements

gRPC

The Java agent now supports gRPC. You will now see transactions, errors, external calls, and distributed traces for all of your gRPC-based clients and services.

Vert.x-3.7

The Java agent now supports Vert.x 3.7. The agent instruments Vert.x Web, Vert.x Core, and Vert.x HTTP client. With this instrumentation, the agent will identify and name your transactions based on Vert.x web routing paths. The agent will also time web handlers, track async handlers, and external calls made with Vert.x HTTP client.

OkHttp 3.14.0

This release adds support for OkHttp 3.14.x. You will now see OkHttp 3.14 calls as external calls in New Relic.

spray-can

The Java agent now supports the spray-can client. The agent will now capture outbound http calls made with the spray-can client and report them as external calls and/or distributed traces.

Embedded Derby 10.15.1.3

The Java agent has expanded support for Derby JDBC up to and including version 10.15.1.3.

JVM monitoring

The Java agent now reports JMX stats for off-heap direct byte buffers. These metrics are available via the JVM page

recordCustomEvent API

The recordCustomEvent API has been updated to accept Map<String,?> as a second parameter instead of Map<String,Object>, allowing maps such as Map<String,String> to be passed without having to cast the type of the map's value.

Fixes

The agent no longer requires a newrelic.yml even when the app_name and license_key configuration options are set via environment variables and/or system properties. For more information, see the Java environment variables documentation.
HttpSessions JMX metrics were not reporting for Websphere Liberty Profile applications.
The transaction_events.max_samples_stored configuration value in the newrelic.yml would incorrectly override the system properties or environment variable values.
Applications running on WildFly 12 - 15 would fail start with NoClassDefFound errors for Java agent classes.
Play applications where external calls inside of future callbacks using async-http-client would not be recorded.
Setting log_limit_in_kbytes would result in the agent not logging to the agent log file if log_file_count was also set to less than 2.
Webflux status codes which were not recognized by Spring Webflux caused a 500 status code to be returned and an exception in application logs.

Known Issues

gRPC: Fixed in 5.1.1

This release contains two bugs in the Java agent's gRPC instrumentation. We highly recommend customers using gRPC instrumentation to upgrade to this and/or later agent versions.

References to transaction segments were not being removed correctly, which can cause a memory leak.
The agent could cause the gRPC server listeners to fail to execute its completed and/or cancelled methods, which can cause unexpected behavior.

Deprecation Notes

Self installer

The New Relic Java agent's self-installer has been removed in order to provide a more consistent user experience. To install the Java agent, add the full path to the newrelic.jar to the -javaagent flag in your JVM options. For more information on installing the agent on specific application servers, Docker, Maven, or Gradle, see the JVM argument documentation.

Deprecated instrumentation

The following instrumentation modules have been moved out of the default Java agent, and are now provided as a separate download. To continue using these modules, just add them to the agent's extensions directory in your newrelic folder or wherever your extensions directory is configured.

Akka 2.0
Akka 2.1
Akka-http 1.0
Akka-http 2.0 - 2.4.1
Akka-http 2.4.2 - 2.4.4
Hystrix 1.2
Hystrix 1.3
Play 1 (instrumentation for Play-1.x is not available as an extension.)
Play 2.0
Play 2.1
Play 2.2
Solr 3.1 - 3.4
Solr 3.5
Solr 3.6

Java agent v5.1.0

Wed, 29 May 2019 00:00:00 +0000

Download this agent version

Improvements

JAX-RS

This release adds support for @PATCH JAX-RS annotation. The agent will create and name transactions based @PATCH annotations.

Fixes

Fixes an issue in the Scala instrumentation that would cause an Java.lang.IllegalArgumentException: to be thrown when the Lightbend Cinnamon agent is in use.
Fixes an issue where Cross Application Tracing headers were incorrectly parsed when Distributed Tracing is enabled. Applications that use both Distributed Tracing and Cross Application Tracing will no longer report external transaction breakdown metrics.
Fixes an issue where the agent’s Kafka instrumentation would report WakeupExceptions as errors in New Relic. These exceptions will no longer be reported.
Fixes a Log4J ClassCastException for applications running on the IBM J9 JVM that set a custom logging manager via the -Djava.util.logging.manager system parameter.
The agent now supports using the thread profiler when the send_environment_info configuration is disabled.

Notes

The agent now sends data to New Relic using gzip compression by default. To use the previous compression set the compressed_content_encoding configuration value to deflate
The jdbc-resultset instrumentation is now disabled by default in the newrelic.yml and will be disabled by default in all future releases.

Known Issues

Fixed in 5.1.1

gRPC

This release contains two bugs in the Java agent's gRPC instrumentation. We highly recommend customers using gRPC instrumentation to upgrade to this and or later agent versions.

References to transaction segments were not being removed correctly, which can cause a memory leak
The agent could cause the gRPC server listeners to fail to execute its completed and/or cancelled methods, which can cause unexpected behavior

Java agent v5.10.0

Wed, 29 Jan 2020 00:00:00 +0000

Download this agent version

Improvements

Support for W3C Trace Context, with easy upgrade from New Relic trace context

Distributed tracing now supports W3C Trace Context headers for HTTP and gRPC protocols when distributed tracing is enabled. Our implementation can accept and emit both W3C trace header format and New Relic trace header format. This simplifies agent upgrades, allowing trace context to be propagated between services with older and current releases of New Relic agents. With this release, W3C trace header format will always be accepted and emitted. New Relic trace header format will be accepted, and you can optionally disable emission of the New Relic trace header format.

The New Relic trace header format can disabled using this config or as documented here: newrelic.config.distributed_tracing.exclude_newrelic_header = true

Also, see Known issues and workarounds.
Cassandra
- This release adds instrumentation for queries in versions 3.8+ of the Datastax Cassandra driver, including slow query support. You’ll see relevant breakdowns in the overview chart, entries on the Databases page, and segments in transaction traces.
AWS Async SDK
- AWS S3 - The Java agent now reports calls to Amazon S3 using the S3AsyncClient as external metrics
- AWS SQS - The Java agent now reports calls to SqsAsyncClient as message queue metrics
- AWS SNS - The Java agent now reports calls to Amazon SQS using SNSAsyncClient as message queue metrics

Fixes

In an effort to modernize our language and improve clarity, we have renamed several config values. The old names will still work for now, but they will all be removed in the next major version.

transaction_tracer.slow_query_whitelist is now transaction_tracer.collect_slow_queries_from

strip_exception_messages.whitelist is now strip_exception_messages.allowed_classes

command_parser.blacklist is now command_parser.disallow
The strip_exception_messages config now excludes nested exception messages
The agent will now use a lightweight tracer for SQL tracers beyond the segment_limit, improving performance in cases with a high number of segments.
The agent would fail to report the Docker containerId for some combinations of systemd and Kubernetes
The agent logger would fail to log with: “ERROR RollingFileAppender 'File': No TriggeringPolicy provided” when newrelic.config.log_file_count>1 and newrelic.config.isDaily=false and newrelic.config.log_limit_bytes=0

Known issues and workarounds

If a .NET agent is initiating distributed traces as the root service, you must update that .NET agent to version 8.24 or later before upgrading your downstream Java New Relic agents to this agent release.

Java agent v5.1.1

Thu, 13 Jun 2019 00:00:00 +0000

Download this agent version

Fixes

gRPC

This release fixes two bugs in the Java agent's gRPC instrumentation. We highly recommend customers using gRPC instrumentation to upgrade to this and or later agent versions.

References to transaction segments were not being removed correctly, which can cause a memory leak
The agent could cause the gRPC server listeners to fail to execute its completed and/or cancelled methods, which can cause unexpected behavior

Java agent v5.11.0

Wed, 18 Mar 2020 00:00:00 +0000

Download this agent version

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

Java agent v5.12.0

Tue, 05 May 2020 00:00:00 +0000

Download this agent version

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

Java agent v5.12.1

Fri, 15 May 2020 00:00:00 +0000

Download this agent version

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.

Java agent v5.13.0

Tue, 16 Jun 2020 00:00:00 +0000

Download this agent version

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.

Java agent v5.14.0

Mon, 27 Jul 2020 00:00:00 +0000

Download this agent version

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.

Java agent v5.2.0

Wed, 26 Jun 2019 00:00:00 +0000

Download this agent version

Improvements

MongoDB

This release adds instrumentation for mongo-java-driver clients created using the MongoClients class Previous versions of the agent only supported the MongoClient() constructor Note: The MongoDB Asynchronous Java Drivers are not yet supported.
Custom request header attributes

The Java agent now provides a new configuration option to report HTTP request header(s) as transaction attributes. See the documentation for more details.
Distributed tracing

Datastore span events now include a db.collection attribute. This field represents the collection or primary table name for the associated query. It is accessible in Insights, Distributed Tracing, and anywhere you get your favorite spans.
GC Time

The Java agent now records time spent waiting for garbage collection during the duration of a transaction and includes the GC time on the corresponding transaction trace as well as the transactions time chart.

This setting is configurable as follows in the newrelic.yml:

transaction_tracer:
    gc_time_enabled: true

Fixes

Fixes an issue where very long-running transactions with a large number of segments would cause an excessive amount of memory usage. The agent will no longer trace segments once the segment_limit has been reached.

Notes

The Java agent now enforces a maximum of 10,000 transaction events per minute.

Java agent v5.4.0

Tue, 27 Aug 2019 00:00:00 +0000

Download this agent version

Notes

x-ray and any x-ray related attributes and identifiers will no longer be available in this version of the java agent. The New Relic x-ray feature reached end-of-life on April 17, 2019

Improvements

OkHttp This release adds support for OkHttp 4.0. You will now see OkHttp calls as external calls in New Relic.
Agent configuration settings set via environment variables will be available on the Environment page.
Improves performance of the Java agent.

Fixes

Transaction Traces would occasionally miss segments when using the spring @Async annotation with servlets.
Jax-RS instrumentation was not starting transactions.
A potential race condition during agent startup that would manifest as a NoClassDefFoundError for internal New Relic classes.
Akka-http instrumentation would attempt multiple retransforms of the same class.
The noticeError API would drop custom attributes that weren't of type String, Number, or Boolean, such as an Enum or other custom types.

Java agent v5.3.0

Wed, 24 Jul 2019 00:00:00 +0000

Download this agent version

Improvements

gRPC

The Java agent now has support for gRPC version 1.22
Dragonwell JDK

The Java agent now fully supports Alibaba's Dragonwell JDK
Azul Zing

The Java agent now supports Azul's Zing JVM
Enables ability to migrate to Configurable Security Policies (CSP) on a per agent basis for accounts already using High-security mode (HSM.

When both HSM and CSP are enabled for an account, an agent (this version or later) can successfully connect with either high_security: true or the appropriate security_policies_token configured.

Fixes

LinkageError for applications using both OpenJ9 and Log4J log manager
ClassNotFoundException for applications that specify a Log4j ContextSelector via the -DLog4jContextSelector system property
Akka-http instrumentation would name transactions incorrectly when using an asynchronous onComplete callback to match routes
The agent’s JaxRS instrumentation did not apply to cases where a concrete class implements the same method from two different interfaces
The agent would not report JMX metrics when one or more composite attributes were null
Race condition that could throw a NullPointerException in the agent log during class transformation
Akka-http path matching instrumentation could produce NullPointerExceptions when using a "repeat" path segment with no values. Transactions that pass some values will report as-is, but transactions that pass no values will be reported with a different segment in the metric name: "().repeat()"
ignore_status_codes system property was not getting applied correctly

Java agent v5.5.0

Wed, 04 Sep 2019 00:00:00 +0000

Download this agent version

New features

Support for Real Time Streaming
- Event data is now sent to New Relic every five seconds, instead of every minute. As a result, transaction, error, and custom events will now be available in New Relic dashboards in near real time. For more information on how to view your events with a five-second refresh, see the real time streaming documentation.
- Note that the overall limits on how many events can be sent per minute have not changed. Also, span events, metrics, and trace data is unaffected, and will still be sent every minute.

Improvements

The Java agent now uses persistent connections when connecting to New Relic, reducing overhead.

Java agent v5.6.0

Tue, 17 Sep 2019 00:00:00 +0000

Download this agent version

New APIs

Added getTraceMetadata(). This provides information about the currently executing trace, including the trace and span ids as well as it’s sampled state
getTraceId(), which provides the currently executing trace’s identifier from the TraceMetadata.
getSpanId(), which provides the span identifier associated with the currently executing span from the TraceMetadata.
isSampled(), returns whether or not the current transaction is part of a sampled distributed trace from the TraceMetadata.
Added getLinkingMetadata(), which provides an opaque map of key/value pairs that can be used to correlate this application in the New Relic backend.

Fixes

Spring Webflux WebClient would not track external calls when constructed with baseUrl(String baseUrl)
The NewRelic.getAgent().getConfig().getValue() api would not check configuration values set via environment variables
The agent’s completable-future instrumentation could hold a reference to Tokens after they were expired, which could cause excessive memory usage.
Error traces could report to the wrong application when auto_app_naming is enabled and there were errors from two different application names getting reported during the same harvest
The agent’s MongoDB instrumentation would instrument the same builder used by the async and reactive-streams drivers, resulting in excessive memory usage and incorrect transaction times. Note: The agent will no longer instrument the sync MongoDB driver if the async and/or reactive-streams drivers are on the application’s classpath.

Java agent v5.7.0

Wed, 25 Sep 2019 00:00:00 +0000

Download this agent version

Improvements

Java 13

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

Bug fixes

Calls to NewRelic.getAgent().getTracedMethod().addOutboundRequestHeaders() will no longer throw an exception if a traced method has started but a transaction has not. This could happen by calling this in a method annotated with @Trace(async=true) before a token is linked.
Updates Guava to the newest release.
NoClassDefFoundError would occur in agent logs when a spring controller is used without a root level RequestMapping annotation.
The gc_time metric, which was enabled by default in version 5.2.0, has now been disabled by default since its results are often misleading.

Java agent v5.8.0

Tue, 29 Oct 2019 00:00:00 +0000

Download this agent version

New features

gRPC
- gRPC error reporting is now configurable
- Response codes, component type, and method type are now recorded as attributes.
- The agent now reports the gRPC status code rather than "translating" to HTTP status codes.
Vert.x
- The Java agent now provides visibility into your applications built using the Vert.x 3.8. The agent instruments Vert.x Web, Vert.x Core, and Vert.x HTTP client. With this instrumentation, the agent will identify and name your transactions based on Vert.x web routing paths. The agent will also time web handlers, track async handlers, and external calls made with Vert.x HTTP client.
XML custom instrumentation
- The custom XML instrumentation XSD has been enhanced to support now include support for specifying leaf tracers.
Class Histogram
- A new Class Histogram extension is now available to report heap memory details as events.
Jedis
- Added support for Jedis 3.0.0 and higher. You can now see your Jedis calls in breakdowns in the overview chart, entries in the Databases tab, and segments in transaction traces.
Lettuce
- Instrumentation modules for Lettuce 4 and 5 are now available via the Java agent incubator.

New OSS SDK

We now have an open source Telemetry SDK for Java for sending telemetry data to New Relic. The current SDK supports sending dimensional metrics to the Metric API and spans to the Trace API.

Fixes

The Solr 7 instrumentation would not report Update JMX metrics.
HttpURLConnection instrumentation produced External metrics only when network methods (getInputStream, getResponseCode) are called.
MongoDB instrumentation would report duplicate metrics when applications invoked MongoClientOptions.build() more than once.

Java agent v5.9.0

Tue, 10 Dec 2019 00:00:00 +0000

Download this agent version

Improvements

AWS SDK
- AWS S3 - The Java agent now reports calls to Amazon S3 using AmazonS3 and S3Client as external metrics
- AWS SQS - The Java agent now reports calls to Amazon SQS using AmazonSQS, AmazonSQSAsync, SqsClient as message queue metrics
- AWS SNS - The Java agent now reports calls to Amazon SQS using AmazonSNS, AmazonSNSAsync, SnsClient as message queue metrics
Distributed Tracing - The agent now supports distributed traces originating from the New Relic Browser agent

Fixes

The ca_bundle_path configuration setting would fail to correctly import certificates when running on IBM J9
Clarified the startup log message about the state of browser monitoring for the current application.
The agent logger would sometimes throw a NullPointerException
The agent would stop reporting Kafka metrics when one or more clients where closed
HttpURLConnection instrumentation could cause a NullPointerException in the agent logs and fail to report External metrics

Deprecated

Jar Collector system properties prefixed with newrelic.config.module and environment variables prefixed with NEW_RELIC_MODULE are deprecated and will be removed in a future agent release. Instead use the newrelic.config.jar_collector and NEW_RELIC_JAR_COLLECTOR prefixes.

Removed dependency

The agent no longer has a dependency on ANTLR.

Java agent v6.0.0

Wed, 26 Aug 2020 00:00:00 +0000

Download this agent version

Improvements

Register an MBean to expose the agent linking metadata.
Support for okhttp 4.4 instrumentation.
Improve reconnect behavior by not pinning to preconnected collector host instance.

Fixes

Fix for asynchronous jar file collection. Collection of modules will no longer block the initial first harvest.
Fix for Real Time Streaming. The first Real Time Streaming harvest will no longer be delayed by 30 seconds.
Fix for reactor-netty verifier versions
Fix race condition around connection pool exhaustion by separating pool timeout from connection timeout.

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.

Java agent v6.1.0

Wed, 30 Sep 2020 00:00:00 +0000

Download this agent version

Improvements

Java 15

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

APIs

New Segment.addCustomAttribute(...) APIs have been added for adding attributes directly to spans.
Newrelic.addCustomParameter API now supports boolean values

Fixes

The agent would try to read environment variables using system-property syntax. It will now log the correct syntax and ignore the incorrect value.

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.

Java agent v6.2.0

Tue, 10 Nov 2020 00:00:00 +0000

Download this agent version

New features

Adds support for Akka Http Core 10.2.0. Thank you jobicarter for reporting this issue.
Adds support for gRPC 1.30.0. Thank you jef for submitting this request and trying it out.
Adds support for map and flatmap async external calls in spring webflux framework. Previously the agent didn’t support client calls that occurred within the map or flatmap methods within the spring webflux framework. External calls such as serviceB and serviceC in the example below would not get reported to New Relic:

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

Adds support for Play 2.16.3. Many thanks to junder31 for this contribution.

Improvements

The agent now supports parsing cgroup ids that do not contain docker-. Previously, the agent only supported docker cgroup ids that contained docker- in them, such as 1:cpu:/system.slice/docker-12345abcde.scope. The agent now supports parsing cgroup ids such as 1:cpu:/system.slice/crio-12345abcde.scope.

Fixes

Prevents the agent from logging a timeout exception when using New Relic Edge with Infinite Tracing but the agent hasn’t sent spans in a while.
Prevents the agent from logging a socket exception when trying to retrieve cloud provider information in a non-cloud environment.
Adds New Relic EU certifications if ca_bundle_path is specified. This fix also came with the reintroduction of the use_private_ssl config, which can be set to add our agent certs to the truststore.

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.

Java agent v6.3.0

Thu, 17 Dec 2020 00:00:00 +0000

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

Java agent v6.2.1

Tue, 17 Nov 2020 00:00:00 +0000

Download this agent version

Fixes

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

Java agent v6.4.0

Wed, 27 Jan 2021 00:00:00 +0000

Download this agent version

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

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.

Java agent v6.4.1

Tue, 02 Feb 2021 00:00:00 +0000

Download this agent version

Fixes

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

Java agent v6.4.2

Tue, 02 Mar 2021 00:00:00 +0000

Download this agent version

Fixes

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

Java agent v6.5.0

Mon, 26 Apr 2021 00:00:00 +0000

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.

Java agent v6.5.1

Fri, 10 Dec 2021 00:00:00 +0000

Download this agent version

Fixes

Upgraded log4j to 2.15.0 to mitigate the security vulnerability CVE-2021-44228. 605

Recommended Java versions

Log4j 2.15.0, which fixes the security vulnerability CVE-2021-44228, is only compatible with Java 8+. Therefore, this version of the agent is not compatible with Java 7 and is only recommended if you are using Java 8+ and are otherwise unable to upgrade to Java agent 7.4.1.

Mitigation for Java 7

Java agent versions 4.12.0 through 6.5.0 (which support Java 7) use Log4j 2.11.2 which falls into the affected range. For Java 7 users the recommended mitigation from Apache Log4j Security Vulnerabilities is to set the system property -Dlog4j2.formatMsgNoLookups=true.

Mitigation: In releases '>='2.10, this behavior can be mitigated by setting the system property log4j2.formatMsgNoLookups. For releases '>='2.7 and '<='2.14.1, all PatternLayout patterns can be modified to specify the message converter as %m{nolookups} instead of just %m. For releases '>='2.0-beta9 and '<='2.10.0, the mitigation is to remove the JndiLookup class from the classpath:

zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class

Note: The alternate approach of defining the LOG4J_FORMAT_MSG_NO_LOOKUPS=true environment variable will not work with the NR Java Agent.

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.

Java agent v6.5.2

Wed, 15 Dec 2021 00:00:00 +0000

Download this agent version

Fixes

Changed log4j version to 2.12.2 to mitigate the security vulnerability CVE-2021-45046. 605

Mitigation for Java 7

This release is compatible with Java 7.

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.

Java agent v6.5.3

Tue, 21 Dec 2021 00:00:00 +0000

Download this agent version

Fixes

Changed log4j version to 2.12.3 to mitigate the security vulnerability CVE-2021-45105. 605

Mitigation for Java 7

This release is compatible with Java 7.

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.

Java agent v6.5.4

Thu, 03 Mar 2022 00:00:00 +0000

Download this agent version

Fixes

Changed log4j version to 2.12.4 to mitigate the security vulnerability CVE-2021-44832. 766

Mitigation for Java 7

This release is compatible with Java 7.

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.

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent.
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

We add new settings to newrelic.yml as we release new versions of the agent. You can use diff or another diffing utility to see what's changed, and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings.

For example, if you diff the default newrelic.yml files for Java agent versions 7.7.0 and 7.8.0, the results printed to the console will be:

➜ diff newrelic_7.7.0.yml newrelic_7.8.0.yml
98c98
<     #forwarding:
---
>     forwarding:
100,101c100,101
<       # When true, application logs will be forwarded to New Relic. The default is false.
<       #enabled: false
---
>       # When true, application logs will be forwarded to New Relic. The default is true.
>       enabled: true

In this example, these lines were added to the default newrelic.yml in Java agent version 7.8.0. If you are moving to 7.8.0 or higher, you should add these new lines to your original newrelic.yml.

Java agent v7.0.0

Wed, 09 Jun 2021 00:00:00 +0000

Download this agent version

New features and improvements:

Real-time profiling for Java using JFR metrics is now fully integrated into the Java agent. See the JFR core README for additional details.

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.

Java agent v7.0.1

Tue, 15 Jun 2021 00:00:00 +0000

Download this agent version

Fixes

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

Java agent v7.1.0

Wed, 07 Jul 2021 00:00:00 +0000

Download this agent version

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.

Java agent v7.10.0

Thu, 15 Sep 2022 00:00:00 +0000

Download this agent version

New features and improvements

Added the following Jakarta EE 9/9.1 compatible instrumentation:

Jetty 11
Tomcat 10
Enterprise Java Beans 4.0
Jakarta RS/WS
Jersey 3+
Jersey Client 3
JSP 3
Servlet 5 & 6
Jakarata.xml
JMS 3
Glassfish 6.0
Open Liberty 21.0.0.12+

Code level metrics

For traced methods in automatic instrumentation or from @Trace annotations, the agent is now capable of reporting metrics with method-level granularity. When the new functionality is enabled, the agent will associate source-code-related metadata with some metrics. Then, when the corresponding Java class file that defines the methods is loaded up in a New Relic CodeStream-powered IDE, the four golden signals for each method will be presented to the developer directly.

Agent log forwarding now adds the following attributes to log events for the log4j2 and logback1.2 frameworks:

thread.name
thread.id
logger.name
logger.fqcn
error.class
error.stack
error.message

Fixes

Fixed an issue with distributed tracing headers not being added on external requests made with the HttpUrlConnection client

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.

Full changelog: https://github.com/newrelic/newrelic-java-agent/compare/v7.9.0...v7.10.0

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent.
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.7.0 and 7.8.0, the results printed to the console will be:

➜ diff newrelic_7.7.0.yml newrelic_7.8.0.yml
98c98
<     #forwarding:
---
>     forwarding:
100,101c100,101
<       # When true, application logs will be forwarded to New Relic. The default is false.
<       #enabled: false
---
>       # When true, application logs will be forwarded to New Relic. The default is true.
>       enabled: true

Java agent v7.1.1

Thu, 15 Jul 2021 00:00:00 +0000

Download this agent version

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.

Java agent v7.11.1

Tue, 15 Nov 2022 00:00:00 +0000

Download this agent version

We recommend updating to the latest agent version as soon as it's available. If your organization has established practices that prevent you from upgrading to the latest version, ensure that your agents are regularly updated to a version at most 90 days old. Read more about keeping your agent up to date.

New features and improvements

Fixes

Fix bug with log4j2 metrics 1068
Adds a previously missing delimiter in POSTGRES_DIALECT_PATTERN "|" 1050
Update snakeyaml lib to v1.33 security patch 1077

Deprecation notice

The following instrumentation modules have been deprecated for removal:

cassandra-datastax-2.1.2
httpclient-3.0
jdbc-embedded-derby-10.10.1.1
jetty-7
jetty-7.6
jetty-9
jetty-9.0.4
jetty-9.1
mongodb-2.12
mongodb-2.14
mongodb-3.0
okhttp-3.0.0
okhttp-3.4.0
okhttp-3.5.0

The httpResponseCode, response.status and response.statusMessage transaction/span attributes are deprecated and will be removed in a future release. These have been replaced by http.statusCode and http.statusText.

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent.
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you are moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml.

Java agent v7.11.0

Thu, 27 Oct 2022 00:00:00 +0000

Download this agent version

New features and improvements

Support Java 19 1022
Support Play 2.8.16+ 981
Support ojdbc8 v21.1.0.0+ 1042
Support Semeru/OpenJ9 JVMs 993
Support log forwarding for java.util.logging (JUL) 1049
Support forwarding log context data 866

The agent can now forward data in Mapped Diagnostic Context (MDC, logback/slf4j) and ThreadContext (log4j2) as attributes when forwarding log records. When the feature is enabled, these attributes will be added to the log records with a context. prefix. For details on how to enable this feature see the documentation for context_data.

Custom Event Limit Increase 1036

This version increases the default limit of custom events from 10,000 events per minute to 30,000 events per minute. In the scenario that custom events were being limited, this change will allow more custom events to be sent to New Relic. There is also a new configurable maximum limit of 100,000 events per minute. To change the limits, see the documentation for max_samples_stored. To learn more about the change and how to determine if custom events are being dropped, see our Explorers Hub post.

Code-level metrics on by default 1037

The code-level metrics functionality introduced with agent 7.10 is now enabled by default. This feature will cause an increase in the consumption of data. The amount depends on the application. To disable code-level metrics, see instructions on our code-level metrics documentation.

Fixes

Prevent an exception from being thrown in the Jedis instrumentation 1011
Improvement on Http4s transactions 1006
Fix noticeError API not verifying whether errors were expected 1014
Adds command for Lettuce queries to clusters 1031
Fix exception when building up the agent jar from a clean repo 1048
Better error handling for code-level metrics 1021 1051
Fix HttpUrlConnection spans not terminating on exception 1053

Deprecation notice

The following instrumentation modules are being deprecated for removal:

cassandra-datastax-2.1.2
httpclient-3.0
jdbc-embedded-derby-10.10.1.1
jetty-7
jetty-7.6
jetty-9
jetty-9.0.4
jetty-9.1
mongodb-2.12
mongodb-2.14
mongodb-3.0
okhttp-3.0.0
okhttp-3.4.0
okhttp-3.5.0

Support statement

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent.
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

Java agent v7.2.0

Thu, 09 Sep 2021 00:00:00 +0000

Download this agent version

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
- Synchronous and asynchronous AWS v2 APIs are auto-instrumented similarly to v1 APIs
- For more information, see Add support for AWS SDK 2 DynamoDB sync/async clients
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.

Disable weaving package when MongoDB 4.x+ reactive driver detected #341
- For more information, see Spring Reactive DB Drivers - MongoDB Support

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.

Java agent v7.3.0

Thu, 30 Sep 2021 00:00:00 +0000

Download this agent version

New features and improvements

Support for Java 16
Auto-instrumentation support for java.net.http.HttpClient
Migrate the Agent’s caching library from Guava to Caffeine (Special thanks to community member Stephan Schroevers for this contribution)
- Caffeine provides an in-memory cache using a Google Guava inspired API. The improvements draw on the author’s experience designing Guava's cache and ConcurrentLinkedHashMap.
- We expect this change to provide improvement in cases where we saw thread contention and deadlocks attributable to the Guava library.

Fixes

Removed support for the anorm-2.0 instrumentation module
- The artifacts that this module instrumented are no longer available.

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.

Java agent v7.4.0

Thu, 28 Oct 2021 00:00:00 +0000

Download this agent version

New features and improvements

Support for Java 17 #433
Distributed tracing is on by default and deprecates cross-application tracing #486
- Increases the default maximum number of samples stored for span events from 1000 to 2000.
- The maximum number of samples stored for span events can be configured via the max_samples_stored configuration in the newrelic.yml.
```
span_events:
  max_samples_stored: 2000
```
This feature causes an increase in the consumption of data. The amount of increase will depend on the application. This feature can be disabled by adding the following to the agent yaml config nested under the common section:
```
distributed_tracing:
  enabled: false
```
Auto-instrumentation support for GraphQL-Java 17.0+ #487
This version tested agent support for the ARM64/Graviton2 platform

Fixes

The existing MongoDB sync client instrumentation was incorrectly applying when MongoDB reactive or async client was being used, which could lead to segment timeouts and long transaction response times. #476

Deprecations and removed features

Cross application tracing is now deprecated, and disabled by default. To continue using it, enable it with cross_application_tracer.enabled = true and distributed_tracing.enabled = false.

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.

Java agent v7.4.1

Fri, 10 Dec 2021 00:00:00 +0000

Download this agent version

Fixes

Upgraded log4j to 2.15.0 to mitigate the security vulnerability CVE-2021-44228. 605

Recommended Java versions

This fix is recommended if you are running on Java 8 - 17.

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.

Java agent v7.4.2

Tue, 14 Dec 2021 00:00:00 +0000

Download this agent version

Fixes

Upgraded log4j to 2.16.0 to mitigate the security vulnerability CVE-2021-45046. 605

Recommended Java versions

This fix is recommended if you are running on Java 8 - 17.

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.

Java agent v7.4.3

Mon, 20 Dec 2021 00:00:00 +0000

Download this agent version

Fixes

Upgraded log4j to 2.17.0 to mitigate the security vulnerability CVE-2021-45105. 605

Recommended Java versions

This fix is recommended if you are running on Java 8 - 17.

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.

Java agent v7.6.0

Mon, 04 Apr 2022 00:00:00 +0000

Download this agent version

New features and improvements

APM logs in context: a quick way to view logs no matter where you are in the platform
- Adds support for logging metrics which shows the rate of log message by severity in the Logs chart in the APM Summary view. This is enabled by default in this release.
- Adds support for forwarding application logs to New Relic. This automatically sends application logs that have been enriched to power automatic logs in context. This is disabled by default in this release. This may be on by default in a future release.
- Adds support for enriching application logs written to disk or standard out. This can be used with another log forwarder to power logs in context if in-agent log forwarding is not desired. We recommend enabling either log forwarding or local log decorating, but not both features. This is disabled by default in this release.
- To learn more about APM logs in context and the configuration options, please see the documentation here. 718
Added instrumentation support for the MariaDB & H2 R2DBC connectors 799 724
Updated agent support for Jedis 4.0.0+ 698
Updated agent support for Cassandra dataStax 4+ 690

Fixes

Guard against intermittent null pointer exceptions 707
Support CSP nonce parameter for RUM header and footer 591
Fixed an issue with auto app naming and distributed tracing transactions 566
Increased maximum TransactionError message size 581
The httpResponseCode, response.status and response.statusMessage transaction/span attributes are deprecated and will be removed in a future release. These have been replaced by http.statusCode and http.statusText 513:

Support statement:

Java agent v7.5.0

Wed, 12 Jan 2022 00:00:00 +0000

Download this agent version

New features and improvements

Update to jfr-daemon 1.7.0 - fixes a memory leak condition by cleaning up copies of JFR recordings. Also updated to use version 0.13.1 of the telemetry-sdk 638
Update HTTP response code attribute names. This will add http.statusCode and http.statusText to spans and transactions 513
Provide support for Datastax/Cassandra WrappedStatments. 525
Add instrumentation for gRPC 1.40.0+ 518
Add suppressed exceptions to ThrowableError.stackTrace 405
Add Scala instrumentation and Scala API for Monix Tasks 543
Add instrumentation for Mongo async/reactivestreams drivers versions 3.4.x to 4.1.x 609
Scala Cats Effect 3 - modified the API to support passing the transaction by implicit reference, rather than using ThreadLocal variables 578
Add Instrumentation for Play WS 2.6.0 under Scala 2.13 594
Agent optimization: change String.replaceAll in favor of Pattern.compile 592

Fixes

Upgrade log4j-core version to 2.17.1 to address security vulnerability CVE-2021-44832 625
Enhancements for Spring WebFlux and Reactor Netty instrumentation to address gaps in instrumentation. Also includes support for upgraded Spring Security configurations 538
Update Async-Http-Client library version to 2.0.35 to address security vulnerability CVE-2017-14063 577
Handle null pointer exceptions in hostname lookup 587
Properly expire tokens used in CompletableFuture instrumentation to reduce memory usage and prevent telemetry reporting delays 634
Add additional exception handling to catch ConnectionPoolTimeoutException errors, which may lead to an unrecoverable agent state 637
Resolve Solr FilterCache Memory Leak 613
Reintroduce MongoDB sync instrumentation (erroneously removed in a prior release while async support was added) 635
Fix Sql obfuscation so that it applies correctly to queries with certain formatting 632
Agent configuration expected_status_codes is not honored when a transaction exception is encountered 565
Scala Cats Effect - ensure Http4s transaction tracer is created on request run. This resolves some invalid tracer states that were causing null pointer exceptions 530
Fix Akka HTTP bindFlow 555
Address Caffeine cache causing memory leak and OOM condition 593

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.

Java agent v7.7.0

Tue, 03 May 2022 00:00:00 +0000

Download this agent version

New features and improvements

Supports Java 18 813
APM logs in context. Automatic application log forwarding is now enabled by default. This version of the agent will automatically send enriched application logs to New Relic. To learn more about this feature see Java: Configure logs in context, and additional configuration options are available Java agent configuration: Config file. To learn about how to toggle log ingestion on or off by account see Disable automatic logging 817
Added instrumentation support for the Postgres, MySQL, Oracle & MSSQL R2DBC connectors 810, 816, 829, and 828

Fixes

Patches a security issue related to an older version of jszip that is included in the Java agent API Javadoc jar 820

Support statement:

Java agent v7.8.0

Thu, 16 Jun 2022 00:00:00 +0000

Download this agent version

New features and improvements

Updated the agent to use caffeine 2.9.3 832
Refactored the log.level attribute name on LogEvents to instead be level 858
Kafka instrumentation - supports metrics for kafka-clients versions 3.x. 860 and 865
Update to jfr-daemon 1.8.0 869
Lettuce instrumentation - supports lettuce-core 4.3 up to 6.x. Please remove any other (experimental/incubating) lettuce extensions or else Redis database metrics could be doubled. 872

Fixes

Fixed CQLParser getOperationAndTableName exception handling. Exceptions are now handled within the CQLParser. 857
Removed akka-http-core bindAndHandle instrumentation to resolve scenarios where duplicated transactions could result 850 (see Scala Akka HTTP core instrumentation for more details)

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.

Java agent v7.9.0

Thu, 28 Jul 2022 00:00:00 +0000

Download this agent version

New features and improvements

Where applicable, existing instrumentation has been tested and verified as compatible with Jakarta EE 8. 900
Add new instrumentation to support Jetty 10. 936
Update to jfr-daemon 1.9.0 to address CVE-2020-29582 and improve CPU overhead. 937
Add support to pass a boolean environment variable NEWRELIC_DEBUG where setting it to true activates the debug configuration. 890
Improved performance by internally replacing regex replace with iterative char replace (thanks to @zowens for this contribution) 933

Fixes

Update the httpurlconnection instrumentation to use newer distributed tracing APIs so that spans are correctly marked as external calls in distributed traces and contain the expected http.* attributes. 885
Illegal Access Exception is no longer thrown from apps using NR agent with scala 2.12 and Java 11. 876

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.

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent.
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.7.0 and 7.8.0, the results printed to the console will be:

➜ diff newrelic_7.7.0.yml newrelic_7.8.0.yml
98c98
<     #forwarding:
---
>     forwarding:
100,101c100,101
<       # When true, application logs will be forwarded to New Relic. The default is false.
<       #enabled: false
---
>       # When true, application logs will be forwarded to New Relic. The default is true.
>       enabled: true

Java agent v8.0.0

Thu, 26 Jan 2023 00:00:00 +0000

Download this agent version

This release includes a change to the HttpURLConnection instrumentation that creates a TimerTask to help ensure complete externals reporting. Under some circumstances this may result in a large number of threads being created, which may exhaust the maximum allocated to the JVM, causing it to stop. This issue has been fixed in the 8.0.1 release and it's highly recommended that you update to this version of the Java agent.

New features and improvements

Added support for Slick 3.4.0 on Scala 2.13
Added support for Embedded Tomcat JMX
Updated the Java agent's snakeyaml dependency to 1.33
Added tracer debug logging, which will appear when -Dnewrelic.config.log_level=finest and -Dnewrelic.debug=true are set
Improved logging when using the recordCustomEvent API now includes event type, key and value
Added Log4j1 instrumentation to support auto log forwarding
Added JBoss Logging instrumentation to support auto log forwarding
Real-time profiling for Java using JFR metrics can now be dynamically enabled/disabled via agent configuration

Fixes

Removed leading slash in JCache metric names
Fixed a bug that was preventing Log4j2 metrics from getting disabled properly
Added a missing delimiter in POSTGRES_DIALECT_PATTERN
Fixed a ClassCastException in GraphQL 16/17
Refactored HttpURLConnection instrumentation to fix several bugs that were affecting external calls and distributed traces
Refactored grpc-1.40.0 instrumentation to ensure that tokens were properly being linked across threads
Fixed a bug that was causing transactions to fail to link when the Spring Webclient would timeout and emit a ReadTimeoutException

Removals

The following previously deprecated instrumentation modules were removed:

cassandra-datastax-2.1.2
httpclient-3.0
jdbc-embedded-derby-10.2.1.6
jdbc-embedded-derby-10.10.1.1
jetty-7
jetty-7.6
jetty-9
jetty-9.0.4
jetty-9.1
mongodb-2.12
mongodb-2.14
mongodb-3.0
okhttp-3.0.0
okhttp-3.4.0
okhttp-3.5.0

The previously deprecated httpResponseCode, response.status, and response.statusMessage transaction/span attributes were removed. These have been replaced by http.statusCode and http.statusText. If you've any custom dashboards or alerts that query the httpResponseCode, response.status, and response.statusMessage attributes then they will need to be updated to instead use http.statusCode and http.statusText.

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent.
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you're moving to 7.11.0 or higher, you should add these new lines to your original newrelic.yml.

Java agent v8.0.1

Thu, 23 Feb 2023 00:00:00 +0000

Download this agent version

New features and improvements

Fixes

Various fixes to the HttpUrlConnection instrumentation. See the README for full details 1145.
Ensure that TokenAndRefCount.token is never null 1148.
Correct a possible NullPointerException being thrown when calling addCustomAttributes 1141.
Fix ClassCircularityError when agent attaches 1139.

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent.
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

Java agent v8.1.0

Thu, 13 Apr 2023 00:00:00 +0000

Download this agent version

New features and improvements

Added support for Webflux 6 1181
Added support for Spring JMS 6 1088
Added support for Mongodb Reactive Streams 1164
Added support for Kafka Streams 1170

Support for Kafka Streams comes in two flavors, metrics and spans. Metrics are enabled by default, while spans are disabled by default. To enable spans add the following to your newrelic.yml configuration under the common section:

common:
  class_transformer:
    kafka-streams-spans:
      enabled: true

Error fingerprint - supply your own errors inbox group names 1195

Are your error occurrences grouped poorly? Set your own error fingerprint via a callback function. A new public API method has been added that will accept a user defined proc. The proc will be invoked for each noticed error and whenever it returns a string, that string will be used as the error group name for the error and will take precedence over any server-side grouping that takes place with the New Relic errors inbox. This gives users much greater control over the grouping of their errors. For more information check our API: Error Grouping and APM: Group errors tab pages.
User tracking - associate errors with a user id 1188

You can now see the number of users impacted by an error group. Identify the end user with a new public API method that will accept a string representation of a user id and associate that user id with the current transaction. Transactions and errors will then have a new enduser.id agent attribute associated with them. This will allow agent users to tag transactions and errors as belonging to given user ids in support of greater filtering and alerting capabilities. For more information check the [Newrelic.setUserId ](https://newrelic.github.io/java-agent-api/javadoc/com/newrelic/api/agent/NewRelic.html#setUserName(java.lang.String) documentation and the Track users impacted with errors inbox page.
Invoking token.link() outside a transaction will instrument that method to start an async transaction 1140
The Kafka clients instrumentation has new metrics to list the nodes: MessageBroker/Kafka/Nodes/<node> 1130

Fixes

Fix ClassCircularityError when agent attaches 1137
Fix NullPointerException thrown when calling addCustomAttributes 1115
Make sure TokenAndRefCount.token is never null 1149
Using a time based cache to store database connection data to prevent a memory leak when instrumenting MySQL client with replication 1114
Decreased the number of threads used in the HttpUrlConnection instrumentation 1145
Fix an issue when HttpUrlConnection is used with the legacy cross application tracing 1142
Performance improvement in Netty’s RequestWrapper 1163
Gracefully shutdown the agent if it encounters issues on startup 1136
Fix WeavedMethod and InstrumentedMethod annotations when applied to constructors. 1153
Performance improvements when using Tomcat 1131
Fixed a bug that caused the agent to not report some exceptions 1176
Updated DockerData to increase the number of container IDs detected 1178
Reduce the number of threads used in Kafka clients instrumentation 1056
Grammar changes [1175](https://github.com/newrelic/newrelic-java-agent/pull/1175 and [1190][https://github.com/newrelic/newrelic-java-agent/pull/1190](https://github.com/newrelic/newrelic-java-agent/pull/1190))

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent.
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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.

Java agent v8.11.0

Thu, 11 Apr 2024 00:00:00 +0000

Download this agent version

New features and improvements

Add HTTP/2 support for Netty 4.1.16.Final + 1815
Support external calls inside Spring Reactor call chains 1828
Support for Apache Pekko (i.e. the pekko-actor library). Support for Pekko HTTP coming soon. 1811
Add configuration to allow the OTel SDK integration to be completely disabled 1821

Configuration via yaml:
```
opentelemetry:
  sdk:
    autoconfigure:
      enabled: false
```
Configuration via system property:
```
  -Dnewrelic.config.opentelemetry.sdk.autoconfigure.enabled=false
```
Treat OpenTelemetry @WithSpan annotation as @Trace in the Java Agent API 1841

Fixes

Fix high CPU usage with HttpURLConnection by reverting InboundWrapper changes introduced in 8.10.0 1840
Prevent duplicate HTTP external calls when using the DynamoDB SDK 1827

Deprecations

The browser footer injection APIs have been deprecated and will be removed in a future agent release. The header injection API now adds both the header and footer scripts. 1679

The following instrumentation modules are deprecated and will be removed in the next major release:

aws-wrap-0.7.0
java.completable-future-jdk8
play-2.3
spring-3.0.0
netty-3.4
Struts v1

IAST

Changes

Json Version bump to 1.2.0 207
IAST replay header decryption due to Security Findings 207

Fixes

Fix issue related to the instrumentation of the Rhino JavaScript Engine that occurred while reading the script 211

Changelog: v8.10.0...v8.11.0

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent.
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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.

Java agent v8.10.0

Thu, 28 Mar 2024 00:00:00 +0000

Download this agent version

This version of the agent introduced a bug that can cause significant CPU and memory usage increases and potential deadlocks if your application uses HttpUrlConnection or any libraries that use it under the hood. Agent version 8.11.0 fixes this problem. Alternatively, disabling the HttpUrlConnection instrumentation would prevent the issue. For example, -Dnewrelic.config.class_transformer.com.newrelic.instrumentation.httpurlconnection.enabled=false.

Disabling this instrumentation will have the effect that the client's external calls will not be recorded. We strongly recommend that you use the latest agent versions. They include all the latest code fixes and provide access to the latest platform features.

New features and improvements

Support for Spring Webflux 6.1.x 1761
Support for Spring Batch v4.0+ 1792
Scala 3 API 1772
ZIO 1 instrumentation improvements 1739
Support for ZIO 2 1778
Enhanced clustered Solr JMX metrics 1812
Add transaction GUID to Errors 1813

Fixes

Prevent NullPointerException when setting the user id outside of a transaction 1762
Disallow Real Time Profiling when High Security Mode is enabled 1764
Prevent ClassCircularityErrors in some specific circumstances 1763
Properly removing files when log_daily is enabled 1754
Decreased memory held by the agent when HTTP calls are made 1775
Prevent duplicate DT headers for gRPC 1783
Properly updating how many log messages are sent after configuration change 1784
Prevent exceptions when reading lambda bytecode 1794
Reduce interval for JDBC caches 1809

Deprecations

The browser footer injection APIs have been deprecated and will be removed in a future agent release. The header injection API now adds both the header and footer scripts. 1679

The following instrumentation modules are deprecated and will be removed in the next major release:

aws-wrap-0.7.0
java.completable-future-jdk8
play-2.3
spring-3.0.0
netty-3.4
Struts v1

IAST

Changes

Ning Async HTTP client Support: The security agent now also supports com.ning:async-http-client 1.0.0 and higher 152, 118, 116
Jersey Support: The security agent now also supports Jersey 2.0 and higher 150, 149
Mule Support: The security agent now also supports Mule server version 3.6 to 3.9.x 144, 143
Jetty v12 Support: The security agent now also support Jetty version 12 and higher 106
Lettuce Support: The security agent now also supports Lettuce 4.4.0.Final and higher 125

Fixes

Extract Server Configuration to resolve IAST localhost connection with application for Wildfly server 192
Trustboundary events now will have list of string as parameter schema

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent.
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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.

Java agent v8.11.1

Thu, 25 Apr 2024 00:00:00 +0000

Download this agent version

Features

Update Security Agent to Public Release version 1.2.1

Deprecations

The browser footer injection APIs have been deprecated and will be removed in a future agent release. The header injection API now adds both the header and footer scripts. 1679

The following instrumentation modules are deprecated and will be removed in the next major release:

aws-wrap-0.7.0
java.completable-future-jdk8
play-2.3
spring-3.0.0
netty-3.4
Struts v1

IAST

Update Security Agent to Public Release version 1.2.1 1870
Changelog: https://github.com/newrelic/csec-java-agent/releases/tag/1.2.1

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent..
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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.

Java agent v8.12.0

Thu, 23 May 2024 00:00:00 +0000

Download this agent version

New features and improvements

Add support for Java 22 1819
Add AI Monitoring support for AWS SDK for Java v2 Bedrock Runtime Client versions 2.20.157 and above 1837
Enhance log forwarding to include caused by section 1857
Add support for Pekko Http 1850
Add local decorating for Log4j 2 users utilizing JsonTemplateLayout 1866
Performance improvements on SQL checks 1887

Fixes

Resolve various thread hopping issues with Spring Reactor call chains 1883
Refactor the daily logfile rolling job to support all platforms 1888
Fix Ning memory leak 1903

IAST

Update Security Agent to Public Release version 1.3.0 1896
Changes/Fixes

Deprecations

The browser footer injection APIs have been deprecated and will be removed in a future agent release. The header injection API now adds both the header and footer scripts. 1679
The following instrumentation modules are deprecated and will be removed in the next major release:
- aws-wrap-0.7.0
- java.completable-future-jdk8
- play-2.3
- spring-3.0.0
- netty-3.4
- Struts v1

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent..
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true

Java agent v8.14.0

Wed, 21 Aug 2024 00:00:00 +0000

Download this agent version

New features and improvements

The Java agent supports disabling AI Monitoring at the account/organization level 1972
HikariCP instrumentation now captures additional metrics 1976
Adds new instrumentation module for kafka-clients-metrics-3.7.0 2001
Adds new instrumentation module for jedis-5.0.0 1969
Adds new instrumentation module for vertx-sqlclient-4.4.2 2004
The newrelic-scala-api for Scala 3 will now be published to Maven 1995
New AWS MQ attributes will be added to spans 1977
Clarify Javadoc comments for @Trace API 2009

Fixes

Fixes a netty-reactor issue that was causing high memory usage 1978
Netty instrumentation will start transactions for HTTP/2 requests 1994

Deprecations

The following instrumentation modules are deprecated and will be removed in the next major release:

aws-wrap-0.7.0
java.completable-future-jdk8
play-2.3
spring-3.0.0
netty-3.4
Struts v1

IAST

CSEC Version bump to 1.4.1 2010
Changelog: https://github.com/newrelic/csec-java-agent/releases/tag/1.4.1

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent..
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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.

Java agent v8.13.0

Thu, 11 Jul 2024 00:00:00 +0000

Download this agent version

New features and improvements

Add attributes to AWS SQS spans that allow linking to SQS entities 1954
Add support for Graphql 22.0+ 1912
Add support for JSP v4 1951
Add instrumentation for HikariCP 2.4.0 to replace existing extension module.1964
- Note: If the New Relic HikariCP incubator module is currently in use, delete it from the new relic jar’s extension folder before upgrading to this version of the Java Agent.
Enhance CompletableFuture instrumentation for JDK11+ 1908
Enable RUM script injection via JSP v3 Tag library 1943
Fetch the docker container ID for ECS Fargate instances 1952

Fixes

Fix R2dbc postgresql 0.9.2 instrumentation to prevent memory leaks 1916
Update vertx-web instrumentation to start transactions for HTTP/2 requests 1959
Update JFR Instance Naming to display correct number of JVMs 1928
Close instrumentation gap for akka-http 10.2.0+ 1955
Start transactions in the Jetty12 core server 1950
Clean up dtTracers and externalTracers after exceptions to prevent memory leaks 1902
Add security-related class excludes during normal class transformer creation 1918
Add null checks to vertx 4.5.1 instrumentation 1927

IAST

CSEC Version bump to 1.4.0 1956
Changelog

Deprecations

The browser footer injection APIs have been deprecated and will be removed in a future agent release. The header injection API now adds both the header and footer scripts. 1679

The following instrumentation modules are deprecated and will be removed in the next major release:

aws-wrap-0.7.0
java.completable-future-jdk8
play-2.3
spring-3.0.0
netty-3.4
Struts v1

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent..
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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.

Java agent v8.15.0

Tue, 01 Oct 2024 00:00:00 +0000

Download this agent version

New features and improvements

Addition of AWS Lambda SDK instrumentation 1998
Reporting of Flyway migration events 2021
Add support for using an environment variable for config file location 2022
Support AWS Kinesis V1 and V2 SDKs 2031
Addition of kafka-clients-node-metrics-3.7.0 Instrumentation module 2039
Add instrumentation for glassfish-jul-extension logging library 2049
Java 23 support 2055
Support reporting of ECS Fargate Docker ids 2050
Actuator endpoint transaction naming for Spring Boot 3 2077

Fixes

Slick 3.5.0 instrumentation bug fix 2025
Protect against Http2Headers methods throwing exceptions in Netty instrumentation 2042
Fix an issue where the Kinesis instrumentation is generating ERROR logs due to a NullPointerException 2052

IAST

CSEC version bump to 1.5 2076
Changelog: https://github.com/newrelic/csec-java-agent/releases/tag/1.5.0

Full Changelog: https://github.com/newrelic/newrelic-java-agent/compare/v8.14.0...v8.15.0

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent..
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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.

Java agent v8.16.0

Thu, 14 Nov 2024 00:00:00 +0000

Download this agent version

New features and improvements

Obfuscate JVM properties 2114
The Java agent will now obfuscate values passed to JVM properties. For example: -Dprop=12345 will now be sent as -Dprop=obfuscated. The documentation has information on how to disable obfuscation and how to add exceptions.

Cloud API 2081
The Cloud API allows cloud provider account information to be provided to the agent. This will allow the agent to populate the cloud.resource_id attribute in calls to select cloud services.
The API documentation has information on how to use it programmatically.
This information can also be provided using a configuration option.

Support distributed tracing for Kafka Stream 3.7.x 2095
Report if agent was installed via Azure site extension 2094
Lazy initialization of GUIDs on DefaultTracers 2088
Java HttpClient: Addition of status code to reported externals 2089
AWS Lambda: populate cloud.resource_id using data from Cloud API 2115
Kinesis Data Streams: populate cloud.resource_id 2112
DynamoDB: populate cloud.resource_id 2113

Fixes

Use recordResponseTimeMetric instead of recordMetric 2128
Use WeakReference HttpUrlConnection instrumentation 2082
Fix a bug where Jetty 12 would not properly link distributed traces 2140
Update to JFR daemon 1.13.0 2129
This update changes the HTTP client used, which caused problems with some proxies.

IAST

CSEC version bump to 1.5.1 2076
Changelog: https://github.com/newrelic/csec-java-agent/releases/tag/1.5.1

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent..
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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.

Java agent v8.17.0

Thu, 19 Dec 2024 00:00:00 +0000

Download this agent version

New features and improvements

Add support for jdbc-mariadb 3.0.0 till latest and r2dbc-mariadb 1.1.2 till latest - credit to @dhilpipre - clone of 2142 by @jtduffy in 2146
Auto discover AWS account ID in the DynamoDB instrumentation by @meiao in 2148
Auto discover AWS account ID in the Lambda sdk instrumentation by @meiao in 2167
Support pekko-http on scala 3 for versions 1.0.0 till latest by @kanderson250 in 2163
Allow JFR queue size and harvest interval to be configured via agent config by @jtduffy in 2168 New configs are:

  jfr:
    # The time interval, in seconds, of how often JFR data is sent to New Relic.
    # The default is 10 seconds.
    harvest_interval: 10

    # The size of the queue used to store JFR events. Increasing this can reduce gaps in JFR reported data
    # but can also cause resource issues in the agent or cause data to be dropped if backend pipeline
    # limits are exceeded.
    # See: https://docs.newrelic.com/docs/data-apis/ingest-apis/event-api/introduction-event-api/#limits
    #      https://docs.newrelic.com/docs/data-apis/ingest-apis/metric-api/metric-api-limits-restricted-attributes/
    # Default is 250000
    queue_size: 250000

Add AWS Firehose SDK Instrumentation for versions 2.1.0 till latest by @obenkenobi in 2149
Implement a new instrumentation module for r2dbc-mysql 1.1.3+ by @jbedell-newrelic in 2169
Memory usage reduced for the r2dbc-mssql and m2dbc-mysql modules by @jbedell-newrelic in 2169
Log when multiple, different, traceparent headers found on inbound request and only report invalid parent header count supportability metric when that scenario occurs by @jtduffy in 2154
Expected NPE in noticeTracer no longer logs full stack trace by @jasonjkeller in 2143

Fixes

Resolved a potential token timeout issue with the reactor-3.3.0 module by @jbedell-newrelic in 2169

IAST

CSEC version bump to 1.6.0 2173
Changelog: https://github.com/newrelic/csec-java-agent/releases/tag/1.6.0

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent..
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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.

Java agent v8.19.0

Tue, 11 Mar 2025 00:00:00 +0000

Download this agent version

New features and improvements

2238 Support Adding Labels to APM Forwarded Logs by @deleonenriqueta
2246 Update Config File to Include APM Forwarded Log Labels Options by @deleonenriqueta
2243 Add response attributes for http4s server modules by @kanderson250
2230 Default proxy_scheme setting to "http" by @jtduffy
2259 Add support for server-side application logging configs by @obenkenobi

Fixes

2228 invokeSuspend edge case fix by @kanderson250
2258 Rename and reenable aws sqs modules by @kanderson250
2245 Update JFR service to run as a daemon by @kanderson250

IAST

CSEC Version bump to 1.6.1 2252
Changelog: https://github.com/newrelic/csec-java-agent/releases/tag/1.6.1

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent..
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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.

Java agent v8.18.0

Thu, 30 Jan 2025 00:00:00 +0000

Download this agent version

New features and improvements

2172 Add scala3 source detection by @kanderson250
2185 Vertx: decrease amount of tokens created by @meiao
2199 Instrumentation module for Struts2 v6.7.0 by @jtduffy
2203 Kafka 3.9 support by @meiao
2204 Sqs distributed trace by @obenkenobi
2202 Kafka clients node metrics by @meiao

Fixes

2187 Fix edge case in JsonTemplateLayout with certain escaped sequences by @jtduffy
2191 Correct Apdex on transaction event if an error is present by @jtduffy
2192 Don't add null port to hostname attribute on JFR events by @jasonjkeller
2197 Fix memory issue with httpclient-5.0 instrumentation by @jasonjkeller

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent..
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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.

Java agent v8.2.0

Wed, 03 May 2023 00:00:00 +0000

Download this agent version

New features and improvements

Added support for Java 20 1226

Fixes

Prevented a NullPointerException from the lettuce instrumentation 1204
Fix failure with browser agent auto injection for tomcat versions 8.5.87+ and 9.0.74+ 1225

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent.
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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.

Java agent v8.20.0

Tue, 15 Apr 2025 00:00:00 +0000

Download this agent version

New features and improvements

Support for CRaC 2250
Support for JDK24 2284
Added sampling options when an inbound traceparent exists 2279
- These options define how the agent should handle sampling of spans, depending on sampling decisions that were made for their parent span by an upstream entity. The configuration options remote_parent_sampled and remote_parent_not_sampled specify what to do in the case the parent span was sampled or not sampled, respectively. See the documentation for full configuration details.
Support for Undertow as a stand-alone module 2269
- This instrumentation is disabled by default to avoid conflicts with existing Wildfly instrumentation. To enable this instrumentation for stand-alone Undertow server apps, use the configuration setting:
```
 class_transformer:
   com.newrelic.instrumentation.undertow-server-1.1.0:
     enabled: true
```
Support for Couchbase Client 2203
- If the Couchbase Client Experimental Module is currently in use, remove it from your extensions directory before upgrading to this version of the Java Agent.

Fixes

~Fix netty 'Unknown' transactions 2274~
- ~This fix moves previous netty instrumentation changes behind a feature flag, which provides additional visibility in some cases involving HTTP2 transactions. To reenable this granularity (at the possible cost of seeing ‘Unknown’ transactions), use the config setting~:
```
  netty:
    http2:
      frame_read_listener:
        start_transaction: true
```
Refactor AWS docker id fetch to use 5s timeout 2275
Feature flag to apply Kotlin ArrayIndexOutOfBoundsException fix to all methods 2307
- This fix addresses errors that may be seen when running the Java Agent in an environment where Kotlin suspends functions are used. To use this fix, set the system property -Dnewrelic.config.class_transformer.clear_return_stacks=true
Prevent cache lock for long DB statement parsing 2294
Add config to specify whether java.sql is loaded by platform classloader 2267

Deprecations

The following instrumentation modules are deprecated and will be removed in the next major release:

aws-wrap-0.7.0
java.completable-future-jdk8
play-2.3
netty-3.4
Struts v1

Known issues: This release has a known issue with Netty where 'Unknown' transactions persist, please update to a later version.

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent..
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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.

Java agent v8.21.0

Thu, 29 May 2025 00:00:00 +0000

Known issues: This release has a known issue with certain uses of Netty Reactor that can cause memory leaks. Please consider using another version.

Download this agent version

New features and improvements

Enhances visibility into Reactor Mono.flatMap calls 2308
Adds new instrumentation for Spring-Kafka and distributed tracing when using the core Kafka client library 2312
Adds KafkaConsumerConfig event support for Kafka 3.7+ 2358

Fixes

Fixes the distributed_tracing.sampler config 2330
Fixes an Illegal Access Error that can occur when using Scala 2.12 and JDK 11. In cases where Scala 2.12 is not detectable by the agent (we check the system classloader for this - notably, sbt will load Scala classes into custom Scala loaders), there is also a feature flag to manually enable the fix via system property -Dnewrelic.config.class_transformer.illegal_access_fix=true 2334
Fix netty 'Unknown' transactions 2274 2355
- This fix moves previous netty instrumentation changes behind a feature flag, which provides additional visibility in some cases involving HTTP2 transactions. To reenable this granularity (at the possible cost of seeing ‘Unknown’ transactions), use the config setting:
```
  netty:
    http2:
      frame_read_listener:
        start_transaction: true
```
- 8.20 has a logic error in the agent config so the fix is only official in agent version 8.21 and up.
Adds a restriction on when to add distributed trace headers for SQS messages. This is based on how large the contents of a message is in bytes and the and the size of attributes. Messages with size greater than 251 KB and/or with 9 or more attributes are excluded from getting distributed trace headers added 2353
Allows the org.crac JAR to be shadowed to prevent conflicts with customer environments. 2344
Backports changes made in PR #1927 to prevent NullPointerExceptions to older versions of the vertx-core instrumentation 2327
Prevents excessive transaction segments from being created by HttpUrlConnection method calls (e.g. getInputStream) when they are not associated with an external call. This behavior can be controlled by the following config options: NEW_RELIC_CLASS_TRANSFORMER_COM_NEWRELIC_INSTRUMENTATION_HTTPURLCONNECTION_VERBOSE=false, sys prop -Dnewrelic.config.class_transformer.com.newrelic.instrumentation.httpurlconnection.verbose=false, or equivalent stanza in newrelic.yml. Default setting is true (i.e. non-external getInputStream and other response handler methods will be reported as before). 2365

Security

Upgrades the com.newrelic.agent.java:infinite-tracing-protobuf for better security with infinite tracing 2339
Replaces snakeyaml with com.konloch:safeyaml to address a security vulnerability 2333

Deprecations

The following instrumentation modules are deprecated and will be removed in the next major release:

aws-wrap-0.7.0
java.completable-future-jdk8
play-2.3
netty-3.4
Struts v1

IAST

CSEC Version Update to 1.7.0 2348 Changelog: https://github.com/newrelic/csec-java-agent/releases/tag/1.7.0

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent..
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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.

Java agent v8.22.0

Wed, 09 Jul 2025 00:00:00 +0000

Download this agent version

New features and improvements

Azure ServiceBus 7.15.0 instrumentation by @jbedell-newrelic in 2384
Linking metadata for Azure App services by @jbedell-newrelic in 2399
Connection errors now logged at SEVERE by @jtduffy in 2377
Log and obfuscate invalid keys added as attributes to logs and events by @jtduffy in 2388

Fixes

Relocate IntelliJ annotations library by @meiao in 2383
Support server side sampling_target configuration by @jtduffy in 2386
Remove MonoFlatMapMain Instrumentation to correct potential memory leaks by @deleonenriqueta in 2400

Deprecations

The following instrumentation modules are deprecated and will be removed in the next major release:

aws-wrap-0.7.0
java.completable-future-jdk8
play-2.3
netty-3.4
Struts v1

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent..
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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.

Java agent v8.23.0

Wed, 13 Aug 2025 00:00:00 +0000

Download this agent version

New features and improvements

Update to support v24 of graphql by @jtduffy in 2425
Add lettuce 6.5 instrumentation by @kanderson250 in 2430
Bump commons-lang version to 3.18.0 by @jtduffy in 2421
Add lettuce dbName to datastore params where available by @kanderson250 in 2423
Add an environment variable to skip implementing certain applications. The environment variable name is NEW_RELIC_STARTUP_JAVA_ARTIFACT_SKIPS. The value of it is a comma separated list of main classes, executable jar files or Java based tools/apps that the agent should NOT instrument (e.g. NEW_RELIC_STARTUP_JAVA_ARTIFACT_SKIPS=keytool,myapp.jar,IgnoreThisClass) by @jtduffy in 2433

Fixes

Fix a bug where SQS messages with 8 attributes are not sent to AWS. SQS messages need less then 8 attributes to pass distributed trace headers by @obenkenobi in 2422
Trim the "Subscriptions" bit off the end of the topic name in azure service bus client by @jbedell-newrelic in 2440
Fix AutoConfiguredOpenTelemetrySdk config by @jasonjkeller in 2451

Deprecations

The following instrumentation modules are deprecated and will be removed in the next major release:

aws-wrap-0.7.0
java.completable-future-jdk8
play-2.3
netty-3.4
Struts v1

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent..
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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.

Java agent v8.24.0

Wed, 03 Sep 2025 00:00:00 +0000

Download this agent version

New features and improvements

Support MongoDB Reactive Streams 5.2.0 and up by @obenkenobi in 2465
Jedis 6 support by @kanderson250 in 2466

Fixes

CouchBase: Add skip class to prevent double instrumentation by @jtduffy in 2462
Spring WebClient 5.x: Only wrap headers instead of the entire response by @jtduffy in 2464

Deprecations

aws-wrap-0.7.0
java.completable-future-jdk8
play-2.3
netty-3.4
Struts v1

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent..
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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.

Java agent v8.25.0

Wed, 12 Nov 2025 00:00:00 +0000

Download this agent version

New features and improvements

Adds Java 25 Support by @deleonenriqueta in 2512
Adds support for Logback-1.5.20 by @jtduffy in 2535
Introduces a config option to disable the execution of the call and exec SQL parser regular expressions by @jtduffy in 2490
Adds support for Kotlin Coroutines v1.4+ by @dhilpipre in 2454
Adds support for Kotlin Coroutines Suspend Functions generated outside of Kotlin Coroutines by @dhilpipre in 2456
Introduces a preference config for multiple hosts during datastore detection by @jbedell-newrelic in 2508
Adds a system property to configure the artifact skip function by @jtduffy in 2509
Adds a configuration option allowing Spring Controller transactions to be named using the controller class name and method name by @sharvath-newrelic in 2532
Implements SamplerConfig, centralizing all distributed_tracing.sampler configs into the SamplerConfig by @jasonjkeller in 2529
Updates kafka-clients-spans-0.11.0.0 producer instrumentation to use modern distributed tracing API’s with W3C Trace Context support by @sharvath-newrelic in 2516

Fixes

Fixes parsing of error class names by @sharvath-newrelic in 2497
Fixes a potential memory issue caused by excessively large stack traces in error logging by @jtduffy in 2498
Clarify logging messages for invalid attributes on custom events and logging events by @sharvath-newrelic in 2501

Deprecations

The following instrumentation modules are deprecated and will be removed in the next major release.

aws-wrap-0.7.0
java.completable-future-jdk8
play-2.3
netty-3.4
Struts v1
spring-3.0.0
thrift-0.8
solr-4.0.0
solr-5.0.0
jdbc-inet-merlia
jdbc-inet-oranxo
grails-1.3
rabbit-amqp-1.7.2
rabbit-amqp-2.4.1
rabbit-amqp-2.5.0
rabbit-amqp-2.7.0
glassfish-3
hibernate-3.3
hibernate-3.5
jdbc-jtds

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent..
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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.

Java agent v8.25.1

Wed, 17 Dec 2025 00:00:00 +0000

Download this agent version

Fixes

Fixes Kotlin Coroutine error about third party implementation of CancellableContinuation

Deprecations

aws-wrap-0.7.0
java.completable-future-jdk8
play-2.3
netty-3.4
Struts v1
spring-3.0.0
thrift-0.8
solr-4.0.0
solr-5.0.0
jdbc-inet-merlia
jdbc-inet-oranxo
grails-1.3
rabbit-amqp-1.7.2
rabbit-amqp-2.4.1
rabbit-amqp-2.5.0
rabbit-amqp-2.7.0
glassfish-3
hibernate-3.3
hibernate-3.5
jdbc-jtds

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent.
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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.

Java agent v8.4.0

Thu, 15 Jun 2023 00:00:00 +0000

Download this agent version

New features and improvements

Added a public preview of the Interactive Application Security Testing (IAST) mode of the New Relic Security agent.

The New Relic Security agent IAST mode is in public preview and should only be used in non-production environments.

To learn about how to use IAST, check out our documentation.

By default, the New Relic Security agent IAST mode is completely disabled. To enable it, set both newrelic.config.security.agent.enabled=true and newrelic.config.security.enabled=true.

Full configuration options are detailed below (note that the security section should be indented two spaces under the pre-existing common section in the newrelic.yml config file):

  # New Relic Security vulnerability detection.
  security:
    # Determines whether the security data is sent to New Relic or not. When this is disabled and agent.enabled is
    # true, the security module will run but data will not be sent. Default is false.
    enabled: false

    # New Relic Security provides two modes: IAST and RASP
    # Default is IAST. Due to the invasive nature of IAST scanning, DO NOT enable this mode in either a
    # production environment or an environment where production data is processed.
    mode: IAST

    # New Relic Security's SaaS connection URL
    validator_service_url: wss://csec.nr-data.net

    # To completely disable all security functionality, set this flag to false. This property is
    # read only once at application start. Default is false.
    agent:
      enabled: false

    # These are the category of security events that can be detected. Set to false to disable detection of
    # individual event types. Default is true for each event type.
    detection:
      rci:
        enabled: true
      rxss:
        enabled: true
      deserialization:
        enabled: true

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent.
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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.

Java agent v8.3.0

Thu, 01 Jun 2023 00:00:00 +0000

Download this agent version

New features and improvements

Batch payloads and compression for Infinite Tracing: Enhanced performance by providing option to enable payload compression and batching for Infinite Tracing 1146.
HttpClient v5.0+ support: The Java agent now supports HttpClient version 5.0 and above 1252.
On-the-fly class retransformation: Classes with Trace annotation are now retransformed upon attach, enhancing instrumentation flexibility 1147.
Enhanced logging for Cats Effect 2: Log Cats Effect 2 instrumentation at finest log level 1173.
High-security mode disables user tracking 1261.
Selective RollingFileAppender Usage: The RollingFileAppender is now only used when log_limit_in_kbytes is greater than 0, improving logging efficiency 1228.

Fixes

Fixed Cats Effect 2 logging: Addressed issues with Cats Effect 2 logging for better reliability 1269.

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent.
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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.

Java agent v8.6.0

Thu, 07 Sep 2023 00:00:00 +0000

Download this agent version

New features and improvements

Support latest Wildfly #1373
Support latest JBoss EAP #1336
Spring Cache instrumentation #1458

This new instrumentation module allows you to see how your caches are performing. It provides hit/miss metrics as well as clear and evict. Search "Metrics Explorer" for the new metrics:

Cache/Spring/<cache-provider>/<cache-name>/hits
Cache/Spring/<cache-provider>/<cache-name>/misses
Cache/Spring/<cache-provider>/<cache-name>/clear
Cache/Spring/<cache-provider>/<cache-name>/evict

Kafka client node metrics #1338

This is a new instrumentation for Kafka clients. It provides metrics similar to the existing instrumentation module, but this provides them by node/topic, whereas the existing one only uses topic. This module is disabled by default, check the documentation for more information.

Kafka client config events #1338

This new instrumentation module sends the Kafka configuration as events periodically. This module is disabled by default, check the documentation for more information.

Improved Struts 2 instrumentation #1457

The Struts 2 instrumentation has been refactored to use a newer instrumentation technique, which allows it to be disabled.

Improved code-level metrics for Servlets. #1394
Security Agent: Support for Apache log4j 3.0.0-alpha1.
Security Agent: Support for Commons.jxpath.
Security Agent: Add agent monitoring details and matrix to health check.
Security Agent: Limiting the supported version range for Jetty.

Fixes

Fixed a bug in the Spring instrumentation when OpenFeign was used. #1197
Fixed a bug where utility classes were not weaved. #1073
Fixed a bug where the agent would not properly send its dependencies. #1340
Security Agent: Issue with HealthChecking having empty process stats issue

Deprecations

aws-wrap-0.7.0
java.completable-future-jdk8
play-2.3
spring-3.0.0
netty-3.4
Struts v1 (legacy pointcut instrumentation)

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent.
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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.

Java agent v8.5.0

Thu, 27 Jul 2023 00:00:00 +0000

Download this agent version

Note: This release note has been corrected to remove Struts 2 from the list of deprecations.

New features and improvements

Kafka Connect instrumentation: Adds metrics and transaction tracing for version 2.0.0+ #1324
Kafka: Added metrics to understand the relationship between consumers, producers, topics and nodes #1223
IAST: Limiting the supported version range for Apache log4j due to the new version release of Apache log4j on 21 June 2023 #80
IAST: Support for indication what all API-IDs are scanned or being scanned #80
All existing instrumnetation now supports Jakarta 10 EE

Fixes

Implement the getStatus() method in the NRWrapper class for version 5 and 6 of Servlet instrumentation #1315

Deprecations

aws-wrap-0.7.0
java.completable-future-jdk8
play-2.3
spring-3.0.0
netty-3.4
Struts 1 (legacy pointcut instrumentation)

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent.
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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.

Java agent v8.7.0

Thu, 26 Oct 2023 00:00:00 +0000

Download this agent version

New features and improvements

Adds support for Java 21 1546
Add experimental config option to run the agent with unsupported java versions 1480
Add intrinsic attribute thread.id to spans to allow for faceting queries by thread ID 1513
Include stack traces in client spans 1507
Adds support for getting the containerId from a docker container with Linux cgroup v2. 1529
Add database and external span attributes to correlate to metric data in accordance with Open Telemetry specs. Certain old attributes are removed. 1525

New attributes:
- db.system
- db.operation
- db.collection
- server.address
- server.port
Removed attributes:
- component
- peer.hostname

Add slow transaction detection which can be configured. It is disabled by default. 1542 E.g:

slow_transactions:
  enabled: true
  threshold: 1000 # The threshold is measured in milliseconds

Add instrumentation for r2dbc postgresql 0.9.2 to 0.9.x 1410
Security Agent: Add new configuration to enable/disable low priority instrumentation security.low-priority-instrumentation.enabled for the CSEC agent. Default value is false. 1515
Security Agent: Cassandra DB v3.0+ Support: The Security agent now supports Cassandra DB version 3.0 and above 122
Security Agent: HttpClient v5.0+ Support: The Security agent now also supports HttpClient version 5.0 and above 122
Security Agent: Support for std-out logging 122
Security Agent: Added feature for Daily log rollover 122
Security Agent: Support for logger config: log_file_count and log_limit_in_kbytes 122
Security Agent: Relocating all our instrumentation packages under the package com.newrelic.agent.security.instrumentation.* 122

Fixes

Fixed a bug where a ClassCircularityError was thrown by Sonarqube9.9 1522
Fix a bug where the Java agent fails to detect spring-security-oauth2-client.jar 1462
Fix a bug where Spring 6/ Spring Boot3 does not report underlying exception/stacktrace when a @RestControllerAdvice class is used 1538
Fix HttpUrlConnection instrumentation so segment timing is accurate 1537
Fixes a bug in Spring 6 instrumentation where transactions are incorrectly named in certain scenarios. 1544 Such include:
- "built-in" controllers that don't have @RestController-like annotations, e.g. /actuator/health (see Actuator endpoints)
- custom controllers that don't use @RestController directly (e.g. using custom annotations)
- requests returning 401s / 404s

Add a fix for JBoss EAP / Wildfly where if customers are using the J2EE/Jakarta Management API, the application fails to startup. 1549 This is done by adding the system property com.newrelic.jboss.jsr77.fix and setting it to true. E.g.

-Dcom.newrelic.jboss.jsr77.fix=true

Customers using JBoss EAP 7.4+ or Wildfly 23+ will need to manually configure the io.undertow.servlet module and add java.management as a dependency. This translates to doing the following steps:

Opening the file modules/system/layers/base/io/undertow/servlet/main/module.xml
Adding the XML element <module name="java.management"/> inside the body of the <dependencies> tag

Here is what the configured XML file may look like:

<module name="io.undertow.servlet" xmlns="urn:jboss:module:1.9">
    <resources>
        <resource-root path="undertow-servlet-2.2.5.Final-redhat-00001.jar"/>
    </resources>

    <dependencies>
        <module name="javax.annotation.api"/>
        <module name="sun.jdk"/>
        <module name="javax.servlet.api"/>
        <module name="javax.servlet.jsp.api"/>
        <module name="javax.servlet.jstl.api"/>
        <module name="org.jboss.logging"/>
        <module name="io.undertow.core"/>
        <module name="org.jboss.xnio"/>
        <module name="jdk.unsupported"/>
        <module name="java.management"/>
    </dependencies>
</module>

Resolve missing class exception on Scala instrumentation 1528
Security Agent: Fixed ClassNotFoundException for IOStreamHelper class with Glassfish 122

Security

Update agent dependency commons-codec to v1.13 1548
Update JFR daemon to 1.11.1. This upgrade updates the underlying OkHttp dependency to version 4.12.0 1561

Deprecations

The following instrumentation modules will be removed in the next major release:

aws-wrap-0.7.0
java.completable-future-jdk8
play-2.3
spring-3.0.0
netty-3.4
Struts v1

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent.
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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.

Java agent v8.8.0

Thu, 21 Dec 2023 00:00:00 +0000

Download this agent version

New features and improvements

Add support for Jetty 12, including Jetty’s implementation of the Jakarta EE 8, 9, and 10 specs. 1621
Add support for Vert.x versions 4.0.0 through 4.4.x 1588
Add instrumentation for graphql-java 21 1454
Instrument r2dbc-postgresql 0.9.2 till latest 1413
Reintroduce the legacy HTTP Attributes that were removed in v8.0.0 to support customers with alerts and dashboards that require them 1671 The attributes are:
httpResponseCode
httpResponseMessage
response.status
response.statusMessage

Attribute reporting is configurable via the following means.

YAML:

attributes:
  http_attribute_mode: both

System property:

-Dnewrelic.config.attributes.http_attribute_mode=both

Environment variable:

NEW_RELIC_ATTRIBUTES_HTTP_ATTRIBUTE=both

The configuration options are:

standard : The agent will send new standard attributes. This configuration is recommended but requires that any alerts or dashboards using attributes be updated to use these new attributes. This setting will reduce the amount of ingest used for attribute reporting.
legacy : The agent will send the legacy attributes referenced above. Customers with alerts or dashboard requiring these attributes can continue to be used as-is. This setting will reduce the amount of ingest used for attribute reporting.
both : This is the default configuration, the agent will send BOTH legacy AND standard HTTP attributes. This configuration was intended to support customers that are unable to modify their alerts or dashboards but this configuration will increase data ingest.
Add an interface for our error API. Our error API can now be called via the code NewRelic.getAgent().getErrorApi() 1577
Add log4j2 JsonLayout support and support log4j2 till latest. 1545
Add httpstatus in the external segment for Spring Webclient 1610
Enable slow transaction detection by default and bump the threshold to 10 minutes 1629
Add support for string formatting with JBoss Logging. 1650
Add logic to remove specific classes from being excluded from being weaved if the IAST security feature is enabled. 1453

The affected classes belong in the following formats:

^java/security/.*
^javax/crypto/.* These are crypto classes which can cause class circularity errors if they get too far along in the class transformer.
^net/sf/saxon.*

If you wish to re-include these excluded rules, you can do so via the following means.

YAML:

  class_transformer:
    excludes: ^javax/crypto/.*,^java/security/.*,^net/sf/saxon.*

System property:

-Dnewrelic.config.class_transformer.excludes=^javax/crypto/.*,^java/security/.*,^net/sf/saxon.*

Environment variable:

NEW_RELIC_CLASS_TRANSFORMER_EXCLUDES=^javax/crypto/.*,^java/security/.*,^net/sf/saxon.*

Prevent license_key value from being written to the agent logs when using debug and/or audit_mode logging 1653

IAST

The IAST feature now also supports Async HTTP client version 2 and above 142
Added support for Sun Net HTTP Server 142
JSON version bump to 1.1.1 142
Add critical error logging via LogMessage event 142

Fixes

Fix transaction naming in Spring controllers with a CGLIB proxy. Transactions now use the actual class name as opposed to the proxied class name. 1574
Fix a NullPointerException caused by ServletContext in servlet instrumentation modules. 1636
Fix a memory leak caused by Lettuce instrumentation. Duplicate code for transaction linking has been removed from the Lettuce instrumentation and is handled by netty-reactor instead. 1608
Fix a bug where invalidating a license key causes a memory leak. Reconnection tasks are now capped in the event of a LicenseException. 1606
Fix a NullPointerException caused by RPMServiceManager 1604
Add a workaround for a memory leak that may occur in rare scenarios with instrumentation using the legacy async API in the Java Agent (which async servlets and Jetty Continuations use). 1555

You can configure the option via the following means:

Agent config file (this will update dynamically if the config file is changed)

common: &default_settings
  legacy_async_api_skip_suspend: true

System Property

-Dnewrelic.config.legacy_async_api_skip_suspend=true

Environment Variable

NEW_RELIC_LEGACY_ASYNC_API_SKIP_SUSPEND=true

IAST

DynamoDB v2 issue: missing attribute values for conditionCheck method in case of transactWriteItems operation on DynamoDB 142
Fixed an Insecure cookie attack vulnerability. 142
Never print LicenseKey 142

Deprecations

The following instrumentation modules are deprecated and will be removed in the next major release:

aws-wrap-0.7.0
java.completable-future-jdk8
play-2.3
spring-3.0.0
netty-3.4
Struts v1

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent.
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will display:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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.

Java agent v8.8.1

Thu, 18 Jan 2024 00:00:00 +0000

Download this agent version

Fixes

Fixed a NullPointerException when working with Synthetics headers 1690

Deprecations

The following instrumentation modules are deprecated and will be removed in the next major release:

aws-wrap-0.7.0
java.completable-future-jdk8
play-2.3
spring-3.0.0
netty-3.4
Struts v1

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent.
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, results such as below will print to the console:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

Support statement:

New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Additionally, we will no longer support older releases once they reach end-of-life.

Java agent v8.9.1

Thu, 08 Feb 2024 00:00:00 +0000

Download this agent version

Fixes

Check HttpHost instance for null before dereferencing it when certain execute() methods are called 1722
Do an instanceof check in the complete() method before class cast 1719
Null check on the response object before trying to report an external call 1719

Deprecations

The browser footer injection APIs have been deprecated and will be removed in a future agent release. The header injection API now adds both the header and footer scripts. 1679

The following instrumentation modules are deprecated and will be removed in the next major release:

aws-wrap-0.7.0
java.completable-future-jdk8
play-2.3
spring-3.0.0
netty-3.4
Struts v1

Update to the latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent.
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the New Relic agent directory backed up.

Update agent config differences [#diff]

We add new settings to newrelic.yml as we release new agent versions. You can use diff or another diffing utility to see what's changed and add the new config settings to your old file. Make sure not to overwrite any customizations you've made to the file, such as your license key, app name, or changes to default settings.

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like this:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

In this example, these lines were added to the default newrelic.yml in Java agent version 7.11.0. If you are moving to 7.11.0 or higher, add these new lines to your original newrelic.yml.

Support statement:

New Relic recommends that you upgrade the agent regularly to ensure you get the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.

Java agent v8.9.0

Wed, 31 Jan 2024 00:00:00 +0000

Download this agent version

New features and improvements

Instrumentation for Spring Webclient 5/6 now captures http status code and http status message 1658
Add status code to grpc-1.40.0 client instrumentation 1673
Add config to set the size limit of attributes on custom events (i.e. newrelic.config.custom_insights_events.max_attribute_value). Default size is 255 characters and the max is 4095. 1683
Add Spring instrumentation modules to support proper transaction naming (route + HTTP method) of traditional annotated spring controllers as well as controllers that inherit annotations from interfaces, super classes or custom annotations. Note that because the new instrumentation can change transaction names, enabling this "enhanced transaction naming" is gated by the newrelic.config.class_transformer.enhanced_spring_transaction_naming agent configuration option, which is false by default. Thanks to @mgr32 for their help with validating the naming changes. 1675
Add instrumentation for Vert.x 4.5.x web client and futures 1704

Fixes

Remove erroneous printing of stack trace in SlowTransactionManager 1684
Convert the ProcessPointCut over to a weaver instrumentation module to better handle cases where it is used in a multi-threaded environment. 1685

Removals

Remove support for setting agent config with rarely used lower-case, dotted environment variable names (e.g. newrelic.config.labels). Customers relying on lower-case, dotted environment variables should switch to the standard upper-case, underscore names (e.g. NEW_RELIC_CONFIG_LABELS). There are no changes to documented system property behavior (via newrelic.config., server-side config, YAML, or standard environment variable (via NEW_RELIC_). 1598

Deprecations

The browser footer injection APIs have been deprecated and will be removed in a future agent release. The header injection API now adds both the header and footer scripts. 1679

The following instrumentation modules are deprecated and will be removed in the next major release:

aws-wrap-0.7.0
java.completable-future-jdk8
play-2.3
spring-3.0.0
netty-3.4
Struts v1

IAST

Update Security Agent to Public Release version 1.1.0 1710
Changelog: https://github.com/newrelic/csec-java-agent/releases/tag/1.1.0

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent.
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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.

Java agent v9.0.0

Wed, 14 Jan 2026 00:00:00 +0000

Download this agent version

New features and improvements

Add config to delete stale agent temp jars on startup by @jtduffy in 2676
Add "inclusion" option to compliment the exclude configuration for selectively instrumenting applications @jtduffy in 2638
- To use this feature, set the environment variable NEW_RELIC_STARTUP_JAVA_ARTIFACT_INCLUDES or system property newrelic.config.startup_java_artifact_includes. Specify the artifacts that should be instrumented as a comma-separated list.

Fixes

Resolve IllegalAccessError by moving wrapper class out of S3AsyncClient_Instrumentation by @jtduffy in 2503
Fix mislabeled instrumentation version on log events in logback-classic-1.5.20 by @jasonjkeller in 2594
Fixed logging message for max attribute value by @jeffalder in 2680
Corrected Trace Ratio sampler priorities by @jtduffy in 2583

Removals

Removes deprecated jdbc-inet-* modules by @obenkenobi in 2572
Removes deprecated java.completable-future-jdk8 instrumentation by @obenkenobi in 2562
Removes aws wrap instrumentation by @obenkenobi in 2567
Removes jdbc-sybase-6 module by @obenkenobi in 2614
Removes play 2.3 instrumentation by @obenkenobi in 2568
Removes deprecated thrift-0.8 module by @obenkenobi in 2569
Removes deprecated solr 4.0 & 5.0 modules by @obenkenobi in 2570
Removes deprecated module grails-1.3 by @obenkenobi in 2573
Removes deprecated module hibernate-3.3 by @obenkenobi in 2574
Removes deprecated footer injection API by @sharvath-newrelic in 2620
Removes deprecated Struts 1 pointcuts by @obenkenobi in 2561
Removes deprecated module glassfish-3 by @sharvath-newrelic in 2575
Removes deprecated rabbit-amqp modules 2.5.0, 2.4.1, 1.7.2 by @obenkenobi in 2571
Removes deployment marker function by @jtduffy in 2589

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent..
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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.

Java agent v9.1.0

Thu, 12 Feb 2026 00:00:00 +0000

Download this agent version

New features and improvements

The Java Hybrid Agent: offering a "best-of-both-worlds" experience by combining New Relic’s deep visibility with OpenTelemetry API compatibility. This release includes comprehensive support for the OpenTelemetry Tracing, Metrics, and Logs APIs, as well as standalone library and native framework instrumentation. Key enhancements like Span Links and Events on Spans are now available, ensuring seamless interoperability in mixed-mode environments.
- Hybrid Agent OpenTelemetry API Support by @jasonjkeller in 2711
Enhancements to coroutine ignores by @dhilpipre in 2726
Add agent metadata action - @mvicknr in 2732 2745

Fixes

Fix broken trace propagation with w3c headers by @jasonjkeller in 2299
Fix multihost preference config @jtduffy in 2720
Fixed problem where suspend ignores was not being read by @dhilpipre in 2663

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent..
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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.

Java agent v9.2.0

Wed, 08 Apr 2026 00:00:00 +0000

Download this agent version

New features and improvements

Adds Java 26 support 2734
Adds Serverless mode for AWS Lambda monitoring with the Java agent 2609 2615 2625 2633 2640 2641 2647 2673 2716 2721 2735 2723 2740 2769 2782 2794 2797 2796 2806
Adds new application_logging.forwarding.log_level_denylist config 2764
Implements region aware event/metric ingest URIs 2749 2790
Adds support for associating logs to corresponding entity when enable_auto_app_naming is true 2627
Add opentelemetry-sdk-extension-autoconfigure-1.59.0 instrumentation for OpenTelemetry 1.59.0+ 2786
Adds support for associating adaptive sampler to corresponding entity when enable_auto_app_naming is true 2805
Adds supportability metrics for each entity created when enable_auto_app_naming is true 2808
Implements Cloud Metadata Bypass Proxy config 2791
Adds support for multiple versions of Caffeine in the agent 2807
Adds support for explain plans that utilize SQL arrays 2815
Adds generic 'Queue' as a transport type 2820
Adds support for Reactor Netty Http client calls 2817

Fixes

Fixes an edge case where ill-formed payloads caused an NPE when accessing the sampled field on the NR payload 2762
Expires Tokens when a Reactive Subscription is canceled 2798
Adds logic to manually evict any dead threads from the TheadTracker cache to prevent a memory leak 2811
Resolves a deadlock between harvest thread and JVM shutdown thread 2539

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent..
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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.

Java agent v9.3.0

Thu, 28 May 2026 00:00:00 +0000

Download this agent version

New features and improvements

Add log_level_denylist config to default yaml 2830
Solr 9 JMX module 2821
New centralized token counting strategy for capturing token counts from LLM Responses. 2837
Support for capturing JDBC batch operations; specifically the addBatch() and executeBatch() methods. 2840
XML RPC instrumentation module to replace legacy point cut 2841
Add a new JFR specific config jfr.use_display_name. If set to true, the agent will set the JFR host name to the value in the process_host.display_name configuration. The default is false to preserve old behavior.

If jfr.use_display_name is true but the display_name config is empty, the JfrService will fallback to the old behavior for the host name.

common: &default_settings
  jfr:
    use_display_name: true

2847

Remove unneeded segment creation in java.xmlrpc module 2853

Update aws-bedrock-runtime-2.20 Module with a new token counting strategy for each of the models. 2845

New license key obfuscation algorithm 2864
Support for Micronaut Http Clients versions 3.5.0+ 2834
Support for Apache Camel 3.9.0 and up 2896 2901
Support for Kafka Clients 4.0.0 and up 2896

Internal dependency Log4j Core Upgrade from 2.17.1 to 2.25.4 2833
AWS DAX Support starting from 2.0.0 to latest 2873

Add instrumentation for Spring AI completion and embedding clients for versions 1.0.0 and up. This adds new instrumentation modules:

spring-ai-client-chat-1.0.0
spring-ai-model-1.0.0

2842

Core Tracing - Drop SpanEvents and Re-Parent dropped SpanLinks 2881
Pointcut replacements
- Remove SpringDispatcherPointCut and SpringExceptionHandlerPointCut and instead move the functionality into our Spring instrumentation modules.
- Replace HandlerInterceptorPointCut 2871 2886
Support Micronaut’s BlockingHttpClient 2860

Add support for AI Model Context Protocol 1.0.0 to latest. 2880

Fixes

Fix coroutines instrumentation. Fixes include:
- Better tracking of asynchronous behavior by instrumenting gaps that were found where execution can jump to another thread.
- Better naming on Coroutines and Continuations. Existing naming was too generic. New naming identifies according to whether it is started via runBlocking, async, withContext or launch.
- Removed some utility methods that were no longer used 2802
Fixes excessive number of unexpired async tokens when instrumenting Micronaut. 2792
Resolution of Mule 4.9 IllegalAccessError 2859
Fix a mis-recording of the Instrumented and Kept metrics for Core Tracing, as they were originally being recorded as a time metric. 2881

Update to latest version [#procedures]

To identify which version of the Java agent you're currently using, run java -jar newrelic.jar -v. Your Java agent version will be printed to your console.

Then, to update to the latest Java agent version:

Back up the entire Java agent root directory to another location. Rename that directory to NewRelic_Agent#.#.#, where #.#.# is the agent version number.
Download the agent..
Unzip the new agent download file, then copy newrelic-api.jar and newrelic.jar into the original Java agent root directory.
Compare your old newrelic.yml with the newly downloaded newrelic.yml from the zip, and update the file if needed.
Restart your Java dispatcher.

If you experience issues after the Java agent update, restore from the backed-up New Relic agent directory.

Update agent config differences [#diff]

For example, if you diff the default newrelic.yml files for Java agent versions 7.10.0 and 7.11.0, the results printed to the console will be like:

➜ diff newrelic_7.10.0.yml newrelic_7.11.0.yml
...
107a108,119
>       # Whether the log events should include context from loggers with support for that.
>       context_data:
>
>         # When true, application logs will contain context data.
>         enabled: false
>
>         # A comma separated list of attribute keys whose values should be sent to New Relic.
>         #include:
>
>         # A comma separated list of attribute keys whose values should not be sent to New Relic.
>         #exclude:
>
125a138
>
128c141
<     enabled: false
---
>     enabled: true
...

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.

Java agent v3.44.0

Mon, 06 Nov 2017 00:00:00 +0000

Download this agent version

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.

Improvements

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:

scala_futures_as_segments:
      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.