I understand that shadow facts are created once during building.
Still, the application crashes in less than a minute when shadow facts are
enabled and it runs for hours when they are disabled.
I was assuming it to be related to a corrupted data structure that leaks.
Can you think of such a case?
Are there any limitations for shadow facts (besides them being final)?
On 10/8/07, Mark Proctor <mproctor(a)codehaus.org> wrote:
s erel wrote:
Hello,
I've posted before regarding this issue.
We currently evaluating drools 4.01 for our project. We've noticed that
the perm gen space grows at a rapid rate and that eventually results
in a OOM. When shadow facts are disabled, the problem seems to go away (or
at least not as noticeable as before).
Any ideas?
What is the effect of a shadowed object which itself contains complex
objects that are also involved in a pattern (through inline eval)?
when the system encounters a new Class, and shadow is enabled, it
generates a proxy to that class - however this is a one time operation. The
only way that shadow proxies would continue to be created would be if you
where continually creating or loading new classes or redefinitions of the
old classes.
------------------------------
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.orghttps://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