Yes, and also 4.0.2 did had a memory leak that was fixed in 4.0.3, were
no leak was detected my profiling tools. So make sure you are using 4.0.3.
[]s
Edson
2008/1/7, Paul Smith <paul.t.smith(a)gmail.com>:
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(a)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(a)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(a)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(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/rules-users
>
>
>
> _______________________________________________
> rules-users mailing list
> rules-users(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/rules-users
>
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
--
Edson Tirelli
JBoss Drools Core Development
Office: +55 11 3529-6000
Mobile: +55 11 9287-5646
JBoss, a division of Red Hat @
www.jboss.com