Re: [rules-users] Analysing OutOfMemory, too many RightTuple
Hi Ganesh,
I'm not sure I understand your answer. My problem is on the network of
Tuples that the engine creates on objects in memory. Of course, if I could
retract the EvemetierData and have only a limited set the WM memory would
be smaller and my problem not one any more, but currently this is not an
option.
Regards,
Benoît
2014-06-12 9:56 GMT+02:00 ganeshneelekani [via Drools] <
ml-node+s46999n4030006h53(a)n3.nabble.com>:
Hi,
This occurs mainly when if you not executing retract() ot dispose() on
particular object.
If you have employee as an object , and you are doing a transition using
employee object its better to use retract (employee ), which will remove or
clear an object.
regards
Ganesh Neelekani
------------------------------
If you reply to this email, your message will be added to the discussion
below:
http://drools.46999.n3.nabble.com/Analysing-OutOfMemory-too-many-RightTup...
To unsubscribe from Analysing OutOfMemory, too many RightTuple, click
here
<http://drools.46999.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscr...
.
NAML
<http://drools.46999.n3.nabble.com/template/NamlServlet.jtp?macro=macro_vi...
--
View this message in context:
http://drools.46999.n3.nabble.com/Analysing-OutOfMemory-too-many-RightTup...
Sent from the Drools: User forum mailing list archive at Nabble.com.
Attachments:
- attachment.html (text/html — 2.9 KB)