A workaround in optaplanner 6.0.1 is probably to enforce RETE_OO
(unfortunately ScoreDirectorFactoryConfig#buildKieBase hard codes that, so that's a PITA).

It's fixed in BRMS 6.0.0.GA and optaplanner 6.1.0.Beta1.
optaplanner 6.1.0.Beta1 might be released later this month.

On 19-02-14 13:11, Matteo Mortari wrote:
Ciao, I'm another Drools user also encountering similar OutOfMemory errors with v6.0.1; I'm not 100% sure what is your issue specific to, but this may be related / of interest to your case: https://issues.jboss.org/browse/DROOLS-411

Hope this helps;
Ciao
MM


On Wed, Feb 19, 2014 at 8:20 AM, john poole <jdpoole@gmail.com> wrote:
I've converted some NurseRostering rules, which worked in Drools 5.50, to
OptaPlanner 6.0.1. While it works far better for the time it runs, it uses
up whatever memory I can give it (9GB) and then eventually crashes the GUI.

with:
Exception in thread "AWT-EventQueue-0" java.lang.OutOfMemoryError: GC
overhead limit exceeded

Is there a way to limit how much memory OptaPlanner uses? Or is it likely
that I'm just adding fact to the WorkingMemory in a way that wasn't a
problem in 5.5 but is a problem in 6.0?





--
View this message in context: http://drools.46999.n3.nabble.com/OutOfMemoryError-using-6-0-1-tp4028183.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
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