Hi folks, Still i'm struggling to solve memory issue. My application will hang up after one day due to memory leak. I’m not calling session.dispose() and think it was the main reason behind this. How can I keep events & accumulate number of events inside WM in a particular day without a single static StatefulKnowledgeSession? With kind regards, Mohan -- View this message in context: http://drools.46999.n3.nabble.com/Best-practice-to-use-heap-memory-effect... Sent from the Drools: User forum mailing list archive at Nabble.com.

Let's assume we need to calculate number of Alarm facts/events inserted into WM over particular day. We will keep on adding facts throughout the day. If this count greater than threshold let’s notify somebody. Also we will retract facts/events which are older than 24 hours. Can we handle this situation without single static StatefulKnowledgeSession? Simply can we count number of facts/events in a WM in a particular time using multiple session? So I can call session.dispose() after each insertion. -- View this message in context: http://drools.46999.n3.nabble.com/Best-practice-to-use-heap-memory-effect... Sent from the Drools: User forum mailing list archive at Nabble.com.

Hi Greg, yes that's the way i'm doing right now. To keep this count hope we need to maintain single session. So we can’t dispose session and by the time will we end up with memory exhaust? Thanks a lot. -- View this message in context: http://drools.46999.n3.nabble.com/Best-practice-to-use-heap-memory-effect... Sent from the Drools: User forum mailing list archive at Nabble.com.

Correction: You don't need rules at all. On 01/11/2012, Wolfgang Laun <wolfgang.laun(a)gmail.com&gt; wrote:

interval are not fixed. it should be sysdate+24 hours. (2 AM to next day 2 AM) -- View this message in context: http://drools.46999.n3.nabble.com/Best-practice-to-use-heap-memory-effect... Sent from the Drools: User forum mailing list archive at Nabble.com.

What I meant is 24 hour period start from when event insert into memory. So each event/fact has different 24 hour period. If you take whole picture it is not fixed. Simply can we count number of facts/events in a WM in a particular time using multiple session? So I can call session.dispose() after each insertion. thanks. -- View this message in context: http://drools.46999.n3.nabble.com/Best-practice-to-use-heap-memory-effect... Sent from the Drools: User forum mailing list archive at Nabble.com.

Using multiple sessions is not applicable, it will just (heavily) increase memory requirements. How precise does this have to be? For instance, counting all events arriving in the interval yyyy-mm-dd hh:mm requires 24*60 objects EventsPerMinute per 24 hours. You can keep track on the running total in one single fact. As soon as the oldest EventsPerMinute becomes older that 24hrs, you retract it and reduce the running total. You can reduce the granularity to seconds, if necessary. -W On 01/11/2012, mohan <mohan.narangoda(a)gmail.com&gt; wrote:

Even though i have upgraded my application (jboss-6.1.0.Final, Jboss ESB 4.11,drools-5.3.1.Final,mvel2-2.1.0.drools4) still I’m facing memory leak. Application reached 15 GB heap while it ran 4 hours. While going through series of forum post now I suspect that single StatefulSession cause the damage (without dispose). Still I couldn’t track the approach to use one very large long-running StatefulKnowledgeSession containing all relevant operational data(facts) and trigger reasoning process over my CEP events (especially streaming events). To be more precise below I’ll mention my use case. • I have X number of Cells have to pre-loaded in to WM. • If customer(c1) make a call (voice event) inside Cell(A) need to offer free data product. --> insert customer(c1) to WM • Same customer(c1) not eligible for offer for subsequent calls made inside Cell(A) during next 24 hours. -->After 24 hours customer(c1) fact retract from WM. How can we decide exact time finishes using the session to dispose? How can we achieve above case (fusion sliding window) without single session? -- View this message in context: http://drools.46999.n3.nabble.com/Best-practice-to-use-heap-memory-effect... Sent from the Drools: User forum mailing list archive at Nabble.com.

It sounds like you are putting in facts without allowing them to be expired or retracted. If you keep inserting events over 24 hours, if there is enough of them, it will OOM. Try setting an expiration value for the event type, to force it to expire earlier. Mark On 12 Nov 2012, at 05:20, mohan <mohan.narangoda(a)gmail.com&gt; wrote: