Also make sure that you are either using Stateless Working Memory or if you are using a Stateful Working Memory then make sure you're dereferencing objects. I had a similar issue and it turned out to be me using Stateful WM when I didn't realy need it and not dereferencing the objects. There are a number of tools around to help to identify memory leaks. JRockit has a pretty good tool for helping to isolate issues. That's how I isolated my issues.

http://e-docs.bea.com/jrockit/docs142/userguide/memleak.html

On Jan 7, 2008 3:27 PM, Michael Rhoden < mrhoden@franklinamerican.com> wrote:

Try setting your JVM memory higher. Drools tends to use plenty of memory
as well as perm gen space.

What I use:
-Xmx512m -XX:MaxPermSize=512m

-----Original Message-----
From: rules-users-bounces@lists.jboss.org
[mailto:rules-users-bounces@lists.jboss.org] On Behalf Of heroshaojun
Sent: Sunday, January 06, 2008 9:14 PM
To: rules-users@lists.jboss.org
Subject: [rules-users] Drools 4.02 or 4.03 memory leak?

When I use profiler to test inserting object to WorkingMemory, outmemory
always occurs.

Who can help me?

_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users



_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users

_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users