Bug 1036126 - Avoid memory leak in StatelessKnowledgeSessionImpl when fireAllRules() throws an Exception
Summary: Avoid memory leak in StatelessKnowledgeSessionImpl when fireAllRules() throws...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBoss Rules
Version: 5.3.1
Hardware: All
OS: All
high
high
Target Milestone: GA
: ---
Assignee: Julian Coleman
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1073034
TreeView+ depends on / blocked
 
Reported: 2013-11-29 14:04 UTC by Musharraf Hussain
Modified: 2025-02-10 03:34 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:34:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 995023 0 unspecified CLOSED Memory leak in StatelessKnowledgeSessionImpl#execute when fireAllRules throwing RuntimeException 2025-02-10 03:28:16 UTC
Red Hat Issue Tracker DROOLS-72 0 Major Resolved Potential memory leak in StatelessKnowledgeSessionImpl#execute when fireAllRules throwing RuntimeException 2015-07-14 09:15:35 UTC

Description Musharraf Hussain 2013-11-29 14:04:20 UTC
Description of problem:
- When 'ksession.fireAllRules()' throws RuntimeException, it causes 'ksession' to never release its resources .
This issue is already raised and fixed as per this JIRA [1] and BugZilla for BRMS .

[1] https://issues.jboss.org/browse/DROOLS-72
[2] https://bugzilla.redhat.com/show_bug.cgi?id=995023

Version-Release number of selected component (if applicable):
- Drools 5.x shipped with SOA-P 5.x

How reproducible:
- The issue is quite the same as described in these JIRA [1] and BugZilla [2] . Hence we just need to incorporate the fix to the Drools libraries shipped with SOA-P 5.x

[1] https://issues.jboss.org/browse/DROOLS-72
[2] https://bugzilla.redhat.com/show_bug.cgi?id=995023

Steps to Reproduce:
1. Please follow the issue as described above
2.
3.

Actual results:
- "org.jboss.internal.soa.esb.services.rules.DroolsRuleBaseState" object retaining the bulk amount of Heap space, because of "StatelessKnowledgeSession" doesn't call the "dispose()" method in the wake of an exception being faced. Thus, the underlying resources doesn't get free after the exception has been handled.

Expected results:
- Ideally StatelessKnowledgeSessionImpl.execute(..) method should have the capability to release the resource held up by 'ksession' while an exception takes place, by calling 'ksession.dispose()'
 

Additional info:
- NONE

Comment 6 Red Hat Bugzilla 2025-02-10 03:34:30 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.


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