Java agent v3.9.0

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.

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.

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.