Re: [rules-users] Memory leak in 5.2/5.3

Yes, I got the same exception, you can't remove all listeners from the outside (at least in 5.2.0.Final), that's why I patched the AbstractWorkingMemory class to hardcode the listeners removal inside Drools. But now that I found JBPM 5.1.1.Final that seems to solve the problem in a better way, the memory leak doesn't appear in my tests using that version of jbpm in combination with Drools. -- 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.