Dear all, I am encountering a strange issue that rules fire based on events, which I already considered as expired. As far as I learned from the documentation Drools automatically determines the expiration time of an event based on analyzing the rules (e.g. if there's a temporal operator or aggregation using the event). Ok, i do not use anything of that. My scenario is as follows - for testing purposes I use a pseudo session clock and of course the STREAM mode. - At time 0 I insert an Event A and call fireAllRules - Then I advance the time for 100 seconds - Now I add a further rule by parsing a drl file and adding it to the Knowledge base of my current session - Then, still at time 100 I insert another Event B and call fireAllRules again The rule that I've inserted previously fires but unfortunately twice. Once for event A (which I already considered as expired) and for event B (which is that what I wanted). Even if i use the @expires annotation in my drl this does not work correctly. Do I have to call another method to trigger the expiration in the session. Any suggestions? Ingo p.s. I am using Drools 5.5 final -- View this message in context: http://drools.46999.n3.nabble.com/Strange-behaviour-when-adding-rules-dur... 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

Hi, thanks for the advice. Still does not work.... I've isolated the problem. At the beginning the ksession has just a simple rule (see rule one below) and I add the first event. This is the first DRL file i load with rule one This is the second one And this is the final output For any strange reason the first event still fires for the second rule that is newly added at a later point in time. Since the event is never referenced in a temporal statement I assume that the first event with timestamp 0 is already gone when I add the second rule after 100 seconds. Even if a manually annotate the event with @expires(10s) in both DRL files, it results in the same output. Any ideas? Ingo -- View this message in context: http://drools.46999.n3.nabble.com/Strange-behaviour-when-adding-rules-dur... 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

Ok, this is is the Event class This is the main class The drl with the rule one and this is the second one -- View this message in context: http://drools.46999.n3.nabble.com/Strange-behaviour-when-adding-rules-dur... 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