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
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.