[jboss-jira] [JBoss JIRA] (DROOLS-1771) Serialization is triggering rule multiple times

Christopher Brecht (JIRA) issues at jboss.org
Fri Oct 20 05:04:00 EDT 2017


     [ https://issues.jboss.org/browse/DROOLS-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christopher Brecht updated DROOLS-1771:
---------------------------------------
    Description: 
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 at 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 at 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 at 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 at 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 at 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 at 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 at 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 at 3b569985[value=1,timestamp=Fri Jan 01 03:06:00 CET 2010]

  was:
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 at 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 at 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 at 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 at 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 at 415156bf[value=1,timestamp=Fri Jan 01 03:06:00 CET 2010]

+*WITHOUT SERIALIZATION *+

2017-10-20 10:47:04 INFO  o.d.c.k.b.impl.KieRepositoryImpl - KieModule was added: MemoryKieModule[releaseId=org.default:artifact:1.0.0-SNAPSHOT]
STATE OUT Fri Jan 01 03:03:00 CET 2010 com.reproducer.EventA at 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 at 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 at 3b569985[value=1,timestamp=Fri Jan 01 03:06:00 CET 2010]



>  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
>         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 at 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 at 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 at 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 at 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 at 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 at 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 at 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 at 3b569985[value=1,timestamp=Fri Jan 01 03:06:00 CET 2010]



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)



More information about the jboss-jira mailing list