Have you had a look at capturing the dump from the OOM, and analysing
it using e.g. Eclipse MAT, to find where references are being held?
Jevon
On Wed, Apr 4, 2012 at 1:24 PM, thenim <thenim(a)gmail.com> wrote:
@Mark,
Your code example is exactly what I was doing - however there does appear to
be some reference held somewhere, which is causing frequent full GCs - which
eventually causes the thing to grind to a halt. The moment I change this to
the following:
MyObject o = new MyObject(1);
fh = wm.insert(o);
o.update(2); // update the same object rather than create a new one, note,
equals and hash will return different values now.
wm.update(fh, o);
This problem goes away. I will see if over the next few days if I can put a
simple example together to demonstrate the issue.
--
View this message in context:
http://drools.46999.n3.nabble.com/Possible-memory-leak-in-5-3-with-update...
Sent from the Drools: User forum mailing list archive at
Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users