0 Replies Latest reply on Dec 31, 2012 9:47 AM by csergiu77

    OSB execution tracing memory leak.

    csergiu77
      First of all I did not found a section for Oracle Service Bus so I posted here as part of SOA suite.

      The problem i have is that when i enable Execution tracing for a proxy the memory keeps going up and is not garbage collected.

      I analized the heap dump and i discovered that WLLogRecords are kept (my assumption forming a cycle reference) and they are never released.

      Below is a list with the object that hold most of the memory.

      Any Idea ? Is this a known issue ? Mention that the response payload is quite big (apx 5 MB as soap text payload)

      sun.misc.Launcher$AppClassLoader#1

      46,725,791

      java.util.Vector#3

      45,941,861

      java.lang.Object[]#23193

      45,941,837

      class com.bea.alsb.flow.container.FlowContainer

      26,733,868

      com.bea.alsb.flow.container.FlowContainer#1

      26,733,868

      com.bea.bpel.internal.compiler.CompiledProcessCache#1

      26,706,208

      java.util.concurrent.ConcurrentHashMap#4092

      26,706,196

      java.util.concurrent.ConcurrentHashMap$Segment[]#4096

      26,706,156

      weblogic.logging.WLLogRecord#408

      14,469,655

      weblogic.logging.WLLogRecord#496

      14,469,654

      weblogic.logging.WLLogRecord#474

      14,469,654

      weblogic.logging.WLLogRecord#453

      14,469,654

      weblogic.logging.WLLogRecord#345

      14,469,654

      weblogic.logging.WLLogRecord#499

      14,469,650

      weblogic.logging.WLLogRecord#477

      14,469,650

      weblogic.logging.WLLogRecord#433

      14,469,650

      weblogic.logging.WLLogRecord#348

      14,469,650

      weblogic.logging.WLLogRecord#498

      14,469,645

      weblogic.logging.WLLogRecord#347

      14,469,645

      weblogic.logging.WLLogRecord#432

      14,469,644

      weblogic.logging.WLLogRecord#410

      14,469,644

      weblogic.logging.WLLogRecord#389

      14,469,644

      weblogic.logging.WLLogRecord#368

      14,469,644

      weblogic.logging.WLLogRecord#430