]
Matteo Mortari updated DROOLS-516:
----------------------------------
Attachment: Java_VisualVM_2014-06-05_11-38-12.png
Java_VisualVM_2014-06-05_11-43-06.png
Screenshots with Java VisualVM which shows that with mentioned rule included, memory leaks
do happen.
If mentioned rule is commented out and therefore excluded, application memory use looks
stable.
6.1.0.beta4 and identified a rule pattern inducing memory leaks
---------------------------------------------------------------
Key: DROOLS-516
URL:
https://issues.jboss.org/browse/DROOLS-516
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 6.1.0.Beta3, 6.1.0.Beta4
Reporter: Matteo Mortari
Assignee: Mark Proctor
Attachments: 20140604.anotherleak.zip, Java_VisualVM_2014-06-05_11-38-12.png,
Java_VisualVM_2014-06-05_11-43-06.png
Ciao I'm using 6.1.0.beta4 and I identified in my application a rule pattern inducing
memory leaks. I will attach rule, screenshots, and javacode to replicate the issue.
Steps to replicate identification of issue:
* IF the rule {{After No data received within the last 1 hour Error, now resumed}} is
included, memory leaks happens, and pretty quickly.
* IF such rule is commented out, application do manage to keep alive.
Same problem happens even on 6.1.0.beta3 - I did not test with previous versions.
Thanks a lot in advance,
Ciao
Matteo