]
Artur Kronenberg commented on DROOLS-1014:
------------------------------------------
And more info:
When taking the second rule and removing the entry-point from it, the problem disappears.
It runs as quick as in standalone and seems perfectly happy.
This should do as a workaround for now. But I have no idea why it behaves like that.
So summing up:
entry-points seem to have a weird behaviour when marshalling/unmarshalling that eats up
heaps and heaps of memory. (Or my rules are just rubbish)
Drools OOM when loading session
-------------------------------
Key: DROOLS-1014
URL:
https://issues.jboss.org/browse/DROOLS-1014
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 6.3.0.Final
Environment: Mac OS 10.10.5, Eclipse Mars Release, Java 1.8, Drools 6.3.0.Final
Reporter: Artur Kronenberg
Assignee: Mario Fusco
Priority: Critical
I ran into an issue loading the session from my JPA.
I am getting this stacktrace:
http://pastebin.com/PMKpdBWM
This is happening for this rule:
http://pastebin.com/HZmLmsEH
And this module:
http://pastebin.com/2Q6k73tC
What I am doing is:
1. Create a new session
2. Insert an ApplicationEvent
3. fireAllRules
4. Reload -> OOM
The ApplicationEvent has a list of 6345 facts in there. I load them from a CSV file, and
use drools to insert them into my knowledge base as facts.
When I restart my server and have the session reloaded, it ooms when trying to
deserialize the session.
I am still looking for a workaround. I am not sure what is happening and could not find
any more info at this point.
I am using:
JPA + Hibernate 4.2.21.Final
org.codehaus.btm:btm:2.1.4 as a standalone JTA platform
Let me know if there's any other info needed.
Thanks,
Artur