[
https://issues.jboss.org/browse/DROOLS-1014?page=com.atlassian.jira.plugi...
]
Artur Kronenberg commented on DROOLS-1014:
------------------------------------------
Apologize for the spammyness of this, but I did some more digging. The rule I posted has
one more rule, however I believe it to be not important because there should be no way of
this to ever be called. this rule exists in similar form for 5 different groups.
The complete rule:
http://pasted.co/0f218b41 (I ran out of free pastebins...)
For some reason, if only rule "Insert new MainFacts" exists in my drl file, the
code runs quickly and without a problem.
Adding rule "Group bucket 1 MainFact staggered" however hangs the entire
process. Looking at my memory, it does indeed eat up 4.5 GB (I increased the heap even
more just to see what happens).
So I am now confused as to what my second rule is doing? The "EntryPointEventB"
is not inserted. I only insert 1 event into EntryPointA, then fireAllRules(). Somehow, the
second rule seems to be executed and doing weird things, even though EventB is never
inserted so the rule could never be matched. My logging listener also never prints that a
different rule other than the inserting one is invoked.
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
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)