[jboss-jira] [JBoss JIRA] (DROOLS-1014) Drools OOM when loading session
[
https://issues.jboss.org/browse/DROOLS-1014?page=com.atlassian.jira.plugi...
]
Artur Kronenberg commented on DROOLS-1014:
------------------------------------------
And me again, soz ...
I wrote up a standalone example for you, and I saw some interesting stuff. I don't
know if that is a bug, or if that is known behaviour. I'd love an explanation if you
could :)
Basically the example simulates my problem:
2 event classes
2 rules
2 Entry Points (one per rule)
First event attempts to insert 1000 users. The outcome is interesting:
1. WITH Entry Points for the second rule:
* It runs and tries to persist
* It gets increasingly slow
* It requires a LOT of memory (had to up package size to 128 MB and still could not
persist the session)
* It eventually bombs out with an exception, never finishes, never succeeds
2. WITHOUT Entrypoint for the second rule
* Everything runs smoothly
* All is executed and inserted in 139 ms
* No errors
I assume this can not be intended? Something is wrong in the way entrypoints are handled
when serializing the session information I believe.
Let me know if you need more help reproducing etc.
Artur
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
Attachments: test-standalone.zip
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)