]
Mario Fusco updated DROOLS-1771:
--------------------------------
Sprint: 2019 Week 32-34 (was: 2019 Week 29-31)
Serialization is triggering rule multiple times
------------------------------------------------
Key: DROOLS-1771
URL:
https://issues.jboss.org/browse/DROOLS-1771
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.2.0.Final, 7.3.0.Final
Reporter: Christopher Brecht
Assignee: Mario Fusco
Priority: Major
Attachments: EventA.java, Person.java, Reproducer.java
I attached a reproducer of the problem. If I am executing the rules without serialization
everything is working correctly. You can see the output we expect without serialization.
The EventA at 3:00:30 shouldn’t trigger the rule one at time 3:05:00. Using
serialization, event/rule triggering seems to ignore the temporal order of timed events.
+*WITH SERIALIZATION *+
STATE OUT Fri Jan 01 03:03:00 CET 2010
com.reproducer.EventA@614aeccc[value=1,timestamp=Fri Jan 01 03:02:00 CET 2010]
STATE IN Fri Jan 01 03:05:00 CET 2010
com.reproducer.EventA@444548a0[value=0,timestamp=Fri Jan 01 03:00:30 CET 2010]
STATE IN Fri Jan 01 03:05:00 CET 2010
com.reproducer.EventA@773c0293[value=0,timestamp=Fri Jan 01 03:04:00 CET 2010]
STATE OUT Fri Jan 01 03:07:00 CET 2010
com.reproducer.EventA@319854f0[value=1,timestamp=Fri Jan 01 03:02:00 CET 2010]
STATE OUT Fri Jan 01 03:07:00 CET 2010
com.reproducer.EventA@415156bf[value=1,timestamp=Fri Jan 01 03:06:00 CET 2010]
+*WITHOUT SERIALIZATION *+
STATE OUT Fri Jan 01 03:03:00 CET 2010
com.reproducer.EventA@659925f4[value=1,timestamp=Fri Jan 01 03:02:00 CET 2010]
STATE IN Fri Jan 01 03:05:00 CET 2010
com.reproducer.EventA@562c877a[value=0,timestamp=Fri Jan 01 03:04:00 CET 2010]
STATE OUT Fri Jan 01 03:07:00 CET 2010
com.reproducer.EventA@3b569985[value=1,timestamp=Fri Jan 01 03:06:00 CET 2010]