Java agent release notesRSS

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.

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

  Copy

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

  Copy

• 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

  Copy

• 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

  Copy

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

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.

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

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.

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.

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.

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

  Copy

  If you are running J2SE 5.0, please update to agent version 2.21.3.