Java Release Notes

Recent Java agent release notes are listed below. If you would like a release that has been used extensively with a list of known issues, see Established releases (Java) for download link and version information.

Java Agent Release Notes

Thursday, April 24, 2014 - 12:45 Download

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.

Thursday, April 24, 2014 - 12:42
End of Life

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.

Thursday, March 27, 2014 - 15:06
End of Life

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.

Wednesday, March 5, 2014 - 17:49
End of Life

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

Wednesday, March 5, 2014 - 17:43
End of Life

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

Thursday, January 23, 2014 - 16:53
End of Life

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.

Tuesday, January 21, 2014 - 01:39
End of Life

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.

Thursday, January 16, 2014 - 18:42
End of Life

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 Insights. For more information, see http://newrelic.com/software-analytics

Friday, January 10, 2014 - 21:38
End of Life

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.

Tuesday, January 7, 2014 - 22:53
End of Life

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.

Monday, December 16, 2013 - 16:20
End of Life

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.

Thursday, December 12, 2013 - 01:30
End of Life

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.

Friday, December 6, 2013 - 23:06
End of Life

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
    
Tuesday, December 3, 2013 - 00:05
End of Life

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.

Tuesday, November 5, 2013 - 21:04
End of Life

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.

Monday, October 21, 2013 - 22:49
End of Life

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.

Thursday, October 3, 2013 - 22:13
End of Life

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.

Tuesday, October 1, 2013 - 21:09
End of Life

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 in your Account Settings page, you have the option to download a version of the agent that works with Java SE 5.

Tuesday, September 10, 2013 - 21:21
End of Life

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.

Tuesday, August 13, 2013 - 16:38
End of Life

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.

Pages