Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-64

ksession leak with Timer+Loop+PerProcessInstance

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.0.0.GA
    • 6.x.x
    • jBPM Core
    • ER1
    • Hide
      • Unzip attached 01772218_ksession_leak_timer_loop02.zip
      • mvn test
      • It will print "hello" repeatedly
      • After you confirm several "hello", capture a heap dump
      • Look into the heap dump with an analyzer tool (e.g. MemoryAnalyzer) and see several ksession are retained in the heap
      • It will finally lead to OOME
      Show
      Unzip attached 01772218_ksession_leak_timer_loop02.zip mvn test It will print "hello" repeatedly After you confirm several "hello", capture a heap dump Look into the heap dump with an analyzer tool (e.g. MemoryAnalyzer) and see several ksession are retained in the heap It will finally lead to OOME

      If you have a process with Timer in a loop and run it with PerProcessInstance, ksession instances are held in heap so it results in memory leak.

        1. 01772218_ksession_leak_timer_loop02.zip
          26 kB
        2. EclipseMemoryAnalyzer-path2gc-heapFromBusinessCentral.png
          EclipseMemoryAnalyzer-path2gc-heapFromBusinessCentral.png
          226 kB

            swiderski.maciej Maciej Swiderski (Inactive)
            rhn-support-tkobayas Toshiya Kobayashi
            Marian Macik Marian Macik
            Marian Macik Marian Macik
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: