Java agent release notesRSS

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.

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.

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.

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.

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.

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.

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

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.

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.