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.
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?)
--
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.