Skip to content

Latest commit

 

History

History
41 lines (33 loc) · 1.84 KB

File metadata and controls

41 lines (33 loc) · 1.84 KB
subject releaseDate version downloadLink features bugs security
Java agent
2014-12-22
3.12.1
Play 2 async activity is no longer tracked when transaction is ignored
Reduced GC overhead when monitoring Play 2 applications
Reduced memory usage when inspecting slowest SQL statements
stack_based_naming now false by default
Memory leak when applications using servlets are continuously reloaded inside the JVM
Memory leak with long running transactions performing a high number of external calls
Sometimes with JBoss application servers, two JVMs were being displayed in the UI when there was actually only one
Download this agent version

Improvements

  • Play 2 async activity is no longer tracked when transaction is ignored.
  • Reduced GC overhead when monitoring Play 2 applications.
  • Reduced memory usage when inspecting slowest SQL statements.

Config Changes

  • stack_based_naming now false by default.

    The stack_based_naming in the transaction_tracer section is now false by default. Stack-based naming caused significant overhead in many Scala applications, so it now must be set to true explicitly. Set to true for better naming of trace detail segments in Scala Play applications.

    transaction_tracer:
        stack_based_naming: true
    

Fixes

  • Memory leak when applications using servlets are continuously reloaded inside the JVM.
  • Memory leak with long running transactions performing a high number of external calls.
  • In some cases for JBoss application servers, two JVMs were being displayed in the UI when there was actually only one.