Memory leak with Timer+Loop+PerProcessInstance in BPMS

Solution Unverified - Updated -

Issue

  • My process results in OutOfMemoryError under long-run test. In the heap dump, org.drools.core.impl.StatefulKnowledgeSessionImpl class takes up almost 1.6 GB. If the list is sorted by the number of objects then the org.jbpm.process.instance.timer.TimerInstance is ranked third highest after HashMap and Date classes. The TimerInstance class has 3,652,677 instances. This seems very high compared to the number of active process instances. This leak is observed after changing RuntimeManager strategy from SINGLETON to PER_PROCESS_INSTANCE.

Environment

  • Red Hat JBoss BPM Suite
    • 6.4.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.