Java Agent 3.31.0

Released on: 
Wednesday, August 3, 2016 - 12:17

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.