IIRC there was a bug in Drools Expert 5.3 that was not releasing event listeners correctly that led to a memory leak - it might be related to what you have experienced. IIRC this was fixed for 5.4.

Are you able to try with Drools suite 5.4.0.beta2?

sent on the move

On 7 Feb 2012 23:16, "vadlam" <sreeram.vadlamudi@wellsfargo.com> wrote:

Nicolas,

after we run a build and we see that the heap has not been Garbage
collected, when we try run a second build, it crashes after a few minutes
because it does not have much memory to complete the build.

could it be the case that the package that gets built is getting stored and
not released unless the server is restarted?

what is the expectation around a package that has been built in Guvnor.

How long is it retained in Guvnor memory for subsequent access through a
URL?

The same rules get built in Guvnor 5.2 and memory is subsequently released
after the build.

so, it looks like there is some kind of leak happening ?

to contest my own theory, when a package which is smaller in size is built
in Guvnor 5.3, memory is released after the build.

I wonder what could be happening around that 80-85 heap threshold that is
causing memory to be held back.

--
View this message in context: http://drools.46999.n3.nabble.com/limits-on-number-of-rules-in-Guvnor-in-a-package-loaded-in-knowledge-base-tp3716069p3724291.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users