I recently ran into this issue and I've confirmed through testing that Drools
5.3.0.CR1 in conjunction with JBPM 5.1.1 Final fixes the problem.
We're currently rolling our JVMs nightly to prevent out of memory errors, so
I need to deploy this upgrade to production ASAP. Can anyone tell me what
the target is for the final Drools 5.3.0 release?
--
View this message in context:
http://drools.46999.n3.nabble.com/rules-users-Memory-leak-in-5-2-5-3-tp32...
Sent from the Drools: User forum mailing list archive at
Nabble.com.