[
https://issues.jboss.org/browse/JBRULES-2313?page=com.atlassian.jira.plug...
]
Geoffrey De Smet resolved JBRULES-2313.
---------------------------------------
Resolution: Rejected
Rejecting
- because more information is needed (and not given) to fix it if it is really an
issue(see previous comment by Mark).
- and because many fixes have gone into 5.1, 5.2, 5.3 and 5.4 due to much QA work on
those. So even if it isn't Tomcat's known memory leak, it is likely that is
fixed.
Please reopen if you can reproduce the leak with the latest version and clarify if with or
without Tomcat makes a difference.
Tomcat memery leak with drools 4.0.7 or 5.0.1
----------------------------------------------
Key: JBRULES-2313
URL:
https://issues.jboss.org/browse/JBRULES-2313
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core (expert)
Affects Versions: 4.0.7, 5.0.1.FINAL
Environment: XP tomcat 5.5.9
Reporter: GREFFET Emmanuel
Assignee: Mark Proctor
Priority: Critical
Labels: memory_leak, tomcat
Attachments: AnalyseDrools4&5MemoryLeak.doc, screenshot-1.jpg, tests.zip
Original Estimate: 3 weeks
Remaining Estimate: 3 weeks
The memory is never released !!! (never ever ) when à Stop and Start or restart Tomcat.
A made this test with a simple Drools call with a simple webapp and i tried with 4.0.7
and 5.0.1 drools version. The problem is the same.
We need to stop tomcat process to release memory. Until this stop each Tomcat
"Restart" with a drools call, will never release the memory.
I made graphic with VisualWM, and we can see this problem !
I made a zip of my simple Eclipse project (webapp + drools) and word file for more
information and screen copy of VisualVM.
Thanks for help.
Emmanuel GREFFET ( FRANCE)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira