Bug 904958 - Potential memory leak in jBPM5 integration.
Potential memory leak in jBPM5 integration.
Status: CLOSED NOTABUG
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB (Show other bugs)
5.3.1
Unspecified Unspecified
unspecified Severity unspecified
: ER5
: 5.3.1
Assigned To: tcunning
Marek Baluch
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-01-28 04:33 EST by Marek Baluch
Modified: 2013-02-12 10:27 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-01-28 12:01:27 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Marek Baluch 2013-01-28 04:33:06 EST
Description of problem:

I haven't seen anywhere in the code a call to org.drools.runtime.StatefulKnowledgeSession.dispose() method which should be used to releases all the current session resources.

Please see http://docs.jboss.org/jbpm/v5.3/javadocs/org/drools/runtime/StatefulKnowledgeSession.html#dispose()
Comment 2 tcunning 2013-01-28 12:01:27 EST
As far as I know, we cannot do this.    If you start a process, then dispose the session, when you try to move the process along in the business-central console, it will complain that the process's session was disposed.

Note You need to log in before you can comment on or make changes to this bug.