Bug 904958 - Potential memory leak in jBPM5 integration.
Summary: Potential memory leak in jBPM5 integration.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB
Version: 5.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER5
: 5.3.1
Assignee: tcunning
QA Contact: Marek Baluch
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-28 09:33 UTC by Marek Baluch
Modified: 2013-02-12 15:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-28 17:01:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Marek Baluch 2013-01-28 09:33:06 UTC
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 17:01:27 UTC
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.