i want to accumulate on different properties of my event. i have 3 rules which all work in the same manner , accumulate on that event and then work with that result my rules are all like this rule "Request counting Subject By Id" when $set: Set() from accumulate($neu : RequestCtx() over window:time(1m),countMatchingSubjectIdsInRequest($neu) ) java.util.Map.Entry( $id: key, $count: value > 1 ) from $set then channels["AuthZBlocking"].send(new ItemCacheEntry(new Item((String)$id), new Date(System.currentTimeMillis()+ 20000))); end these rules should work concurrently, depending on the propterties. to test this i wrote... let us assume: Rule1 looks for A.A and if |A.A>1| fire Rule2 looks for A.B and if |A.B>1| fire Rule3 looks for A.C and if |A.C>1| fire i inserted A.A A.A A.B A.B A.C A.C and instead of firing 1,2,3 the engine fires : 1,1,2,1,1,2,1,2 Do i have to influence the agenda , when working on the same eventtype ?? -- View this message in context: http://drools.46999.n3.nabble.com/evaluating-different-aspects-of-the-sam... Sent from the Drools: User forum mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

so the only possibilty would be to insert new events which signals that rule x has been fired ..? How is this related to the accumulate A/B/C problem?

-- View this message in context: http://drools.46999.n3.nabble.com/evaluating-different-aspects-of-the-sam... Sent from the Drools: User forum mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

cause if i would know that there hasnt been a change in the count of, for example, A.A, it shouldnt fire, that leads me to the next question: is an accumulate function excuted by more than one thread ?

it rises if you think of storing such information in the context of the accumulate function directly. like a semaphore, which signals that this entry has already caused something fired in the example: the rule 1 accumulates over attributes of incoming objects (A.A) and also sets a flag if an entry has been changed (count ++) -- View this message in context: http://drools.46999.n3.nabble.com/evaluating-different-aspects-of-the-sam... Sent from the Drools: User forum mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users