Hide Forgot
securitylevel_name: Public When using multiple StatefulKnowledgeSessions created from one KnowledgeBase the used memory keeps growing never being freed although method dispose() is called every time the session is not needed anymore. When creating new KnowledgeBase every time the problem disappears. Doesn't occur in Drools 5.2.0.Final nor BRMS 5.1 but all the DEV builds of BRMS 5.2
BRMS 5.1, Drools 5.2 - used memory is bellow 400MB all the time BRMS 5.2 DEV - used memory grows until hit max memory and throws OOME
Attachment: Added: memleak.zip
Ryan, I believe you picked up Drools 5.2 for this build. If you could mark this as resolved and we'll let it go to QE for retest, I'd appreciate it.
This should be resolved in BRMS 5.2.0 ER1. Please have a check.
Unfortunately the problem persists. I'll include memory usage chart.
The chart shows memory usage over time. The test creates one knowledge base that is used to create new knowledge sessions. For first 30k test runs new stateful knowledge session is created for every test run (and properly disposed in finally block) next 30k runs new stateful knowledge session is created for every thread (= 100 sessions).
Attachment: Added: brms-532.png
I just did a little more testing and it seems that jbpm*.jar are causing the problem. I tried removing them for testing other bug and this problem was resolved.
Link: Added: This issue is incorporated by BRMS-644
I would tidy up the brms-engine binaries folder as BRMS-644 suggested, it should be fixed in the next release.
For fixing Bug 727562 - Missing Drools Flow , jbpm-flow and jbpm-flow-build are still needed to be included. So this issue might still remain and need further investigation.
Could we retest this issue since many jars in binary folder has been cleaned up?
Still present in 5.2.0 ER2. When the jbpm-flow-5.1.1.SOA.ER2.jar and jbpm-flow-builder-5.1.1.SOA.ER2.jar are on classpath the memory consumption is raising until the OOME is thrown.
Fix checked into drools-core 5.2.x branch as well as jbpm 5.1.x branch
Marked as not needing a release as this issue appears to be between internal dev builds. If it should have a release note, please set the technical_not flag to '?' thanks - Lee
Sorry, still getting used to BZ, it looks like I (somehow) changed the component from BRE to 3rd party when I set the technical note flag. Changing it back - sorry. Lee
Petr, please verify that this bug no longer affects our performance tests.
Verified fixed for StatefulKnowledgeSession in 5.2.0 ER3.