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] <[hidden email]>:

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-RightTuple-tp4029988p4030006.html

To unsubscribe from Analysing OutOfMemory, too many RightTuple, click here.
NAML