Uploaded image for project: 'JBoss BPMS Platform'
  1. JBoss BPMS Platform
  2. RHBPMS-5160

[GSS] (6.4.z) VfsMVELWorkItemHandlerProducer leak in EAP 7 with PerRequest/PerProcessInstance

    Details

    • Type: Bug
    • Status: Verified (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 6.4.11.GA
    • Component/s: Business Central
    • Labels:
    • Environment:
      • EAP 7
      • Business Central as a process engine
      • PerRequest/PerProcessInstance
    • Target Release:
    • Fix Build:
      CR1
    • Steps to Reproduce:
      Hide
      • Unzip jboss-eap-7.0-02081187-reproducer.zip (see comment for download link)
      • cd jboss-eap-7.0
      • bin/standalone.sh
      • IMPORTANT: Don't run it inside "bin" directory because ".niogit" is located under "jboss-eap-7.0"
      • Login to business-central (user:bpmsAdmin password:password1!)
      • Go to "Authoring" > "Project Authoring". "example" > "repo2" > "project1"
      • Build&Deploy
      • In "Deploy" > "Process Deployments", confirm it's PER_REQUEST
      • Go to "Process Management" > "Process Definition"
      • Start "helloProcess" * 5 times
      • Capture a heap dump (jmap -dump:format=b,file=heap.bin <PID>)
      • For example, In Memory Analyzer Tool, Search "VfsMVELWorkItemHandlerProducer" in Histogram view. You will see 6 instances of VfsMVELWorkItemHandlerProducer. It will keep increasing as you use ksession.
      • Or you may conveniently check it with jmap -histo:live <PID>
      Show
      Unzip jboss-eap-7.0-02081187-reproducer.zip (see comment for download link) cd jboss-eap-7.0 bin/standalone.sh IMPORTANT: Don't run it inside "bin" directory because ".niogit" is located under "jboss-eap-7.0" Login to business-central (user:bpmsAdmin password:password1!) Go to "Authoring" > "Project Authoring". "example" > "repo2" > "project1" Build&Deploy In "Deploy" > "Process Deployments", confirm it's PER_REQUEST Go to "Process Management" > "Process Definition" Start "helloProcess" * 5 times Capture a heap dump (jmap -dump:format=b,file=heap.bin <PID>) For example, In Memory Analyzer Tool, Search "VfsMVELWorkItemHandlerProducer" in Histogram view. You will see 6 instances of VfsMVELWorkItemHandlerProducer. It will keep increasing as you use ksession. Or you may conveniently check it with jmap -histo:live <PID>
    • Sprint:
      2018 Week 25-26

      Description

      Under the condition:

      • EAP 7
      • Business Central as a process engine (= not kie-server)
      • PerRequest or PerProcessInstance

      The number of org.jbpm.console.ng.bd.util.VfsMVELWorkItemHandlerProducer.VfsMVELWorkItemHandlerProducer instances keep increasing in heap as users use ksession. They are not released even after a process is completed.

      It's reproducible with a simple process.

      VfsMVELWorkItemHandlerProducer instances are held by InjectableRegisterableItemsFactory through org.jboss.weld.context.CreationalContextImpl/org.jboss.weld.context.SerializableContextualInstanceImpl. See attached screenshots.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                cnicolai Cristiano Nicolai
                Reporter:
                tkobayashi Toshiya Kobayashi
                Tester:
                Bojan Sremac
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: