[rules-users] Drools Perm gen grows constantly

[Mark Proctor]

Are you saying the permgen is leaking? That you update the rules, and no perigean space is reclaimed?

There are some issues with the JVM, that I’ve seen before, which may be the problem. Such as the CMSClassUnloadingEnabled issue:
http://java.dzone.com/articles/busting-permgen-myths

I’d be interested to know if this is a pergmen leak, and if it continues on 6.x. If it does, maybe you could work with us to find out why it’s not being reclaimed?

Mark

On 18 Nov 2013, at 16:56, pmander <paul.s.mander at gmail.com> wrote:

> Thanks for clearing this up. The overhead for us is negligible and more
> important that the application is survivable. Using Java as the dialect
> would appear to not be a option for anyone then?
> 
> We are using drools to process around 50Mil transactions against 15k rules.
> This is distributed over 32 nodes to get the end to end performance we need.
> Using java dialect on initial run with a mac perm size of 512Mb copes ok but
> on subsequent runs we run out of perm gen space and the processes take up
> tons of cpu and then run out of memory. For each run we have to recreate the
> knowledge base.
> 
> 
> 
> 
> 
> --
> View this message in context: http://drools.46999.n3.nabble.com/Drools-Perm-gen-grows-constantly-tp4026673p4026812.html
> Sent from the Drools: User forum mailing list archive at Nabble.com.
> _______________________________________________
> rules-users mailing list
> rules-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users