Op 12-02-13 14:47, duggal schreef:
> Can you try 5.5.1-SNAPSHOT?
I tried with 5.5.1-SNAPSHOT from
https://repository.jboss.org/nexus/content/groups/public
The problem still exists
> If you can reproduce with 5.5.1-SNAPSHOT, please file a jira with the
> stacktrace and if possible a way to reproduce.
>
https://issues.jboss.org/browse/DROOLS
I am trying to package the issue into a reproducible test case for the JIRA.
Great.
In the jira, be clear that you're reporting the mvel problem, not
the planner score corruption.
Once the mvel problem is fixed, we can start looking at the planner
score corruption, if it's still there (and isn't caused by the mvel
problem).
I have tried different combinations of large and small data and have the
following observations -
1. The data corruption happens when a limit on the number of problem facts
is crossed. This leads me to believe that insertion of a large amount of
data in the working memory is causing this issue.
2. I am running the planner within a server side library. Each time i invoke
the optimization routine and suffer this error, the server process memory
keeps increasing. This indicates that memory is not being released
(corruption?)
Sounds like a memory leak (= serious issue), which has normally
unrelated to score corruption.
--
View this message in context:
http://drools.46999.n3.nabble.com/Drools-Planner-5-5-0-Final-Memory-corru...
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