You may have to dispose the sessions explicitly - or even the knowledgebase,
using the internal method that was added as a temporary "brute force" patch
to leaks in 5.6.
The composite classloader was replaced in 6.x, so the newer versions should
not have this kind of problems.
Best
Davide
--
View this message in context:
http://drools.46999.n3.nabble.com/rules-users-Memory-leak-due-CompositeCl...
Sent from the Drools: User forum mailing list archive at
Nabble.com.