Normally a Fusion session is created once, possibly initialized with some static facts, and then you use the entry point to insert events, call fireAllRules, and wait for the next event to arrive from its source. Therefore, keep the session and the entry point for repeated use by the last two statements. -W On 22 October 2010 06:08, Pankaj Khattar <pankaj.khattar1(a)alcatel-lucent.com

This is more a Java question than a Drools specific problem. You have several producers, running in threads, parallel or (more or less) one after the other. You have one consumer, the thread running the single session. Consuming consists of accepting the fact and inserting it into the session; then fireAllRules must be called; then the Consumer is ready for the next fact. Look into java.util.concurrent. One object implementing BlockingQueue<?> is what you need for communication between producers and the consumer. You'll have to figure out the details, depending on the runtime parameters of your application, i.e., arrival frequency, average processing time by the Engine, etc. -W On 22 October 2010 08:10, Ayush <ayush.vatsyayan(a)alcatel-lucent.com&gt; wrote:

Thank you for your reply. I think I was heading into the wrong direction. Now when I've synchronized the function which is creating session, session is static and is only called once, and firing the rules it's working fine. I'm planning to use JMS wherein consumer will be syncronized. Is this the right way? But I've following rule rule "TwoAlertsFromSameSource" no-loop true dialect "mvel" when $RA : AlertReceivedEvent( severity == 2, $entityA : entity ) over window:time(60s) from entry-point NotificationStream $RB : AlertReceivedEvent( this != $RA, severity == 1, $entityB : entity ) over window:time(60s) from entry-point NotificationStream $alertB : X733Alert(this.entity == $entityB, correlationState != CorrelationStates.ROOT_CAUSE) $alertA : X733Alert(this.entity == $entityA, correlationState != CorrelationStates.SYMPATHETIC) then System.out.println("#### Running TwoAlertsFromSameSource... ####"); modify($alertB) { setCorrelationState("Main"); } System.out.println("correlation state "+$alertB.getCorrelationState()); modify($alertA) { setCorrelationState("Lower"); } end In above rules it's unable to modify $alertB. I'm working on it and hoping that this also comes out to be java problem. -- View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Error-Inserting-event... Sent from the Drools - User mailing list archive at Nabble.com.

Thanks a lot Wolfgang for your prompt reply. I'm able to move forward now -- View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Error-Inserting-event... Sent from the Drools - User mailing list archive at Nabble.com.

Thank you for your reply. I think I was heading into the wrong direction. Now when I've synchronized the function which is creating session, session is static and is only called once, and firing the rules it's working fine. I'm planning to use JMS wherein consumer will be syncronized. Is this the right way? But I've following rule rule "TwoAlertsFromSameSource" no-loop true dialect "mvel" when $RA : AlertReceivedEvent( severity == 2, $entityA : entity ) over window:time(60s) from entry-point NotificationStream $RB : AlertReceivedEvent( this != $RA, severity == 1, $entityB : entity ) over window:time(60s) from entry-point NotificationStream $alertB : X733Alert(this.entity == $entityB, correlationState != CorrelationStates.ROOT_CAUSE) $alertA : X733Alert(this.entity == $entityA, correlationState != CorrelationStates.SYMPATHETIC) then System.out.println("#### Running TwoAlertsFromSameSource... ####"); modify($alertB) { setCorrelationState("Main"); } System.out.println("correlation state "+$alertB.getCorrelationState()); modify($alertA) { setCorrelationState("Lower"); } end In above rules it's unable to modify $alertB. I'm working on it and hoping that this also comes out to be java problem. -- View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Error-Inserting-event... Sent from the Drools - User mailing list archive at Nabble.com.