[jboss-jira] [JBoss JIRA] (DROOLS-1537) Scheduled activations are rescheduled as if new when unmarshalling session in Drools 6.5

[Kay J (JIRA)]

    [ https://issues.jboss.org/browse/DROOLS-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398350#comment-13398350 ] 

Kay J commented on DROOLS-1537:
-------------------------------

So I have to use the same kBase instead of creating a new one? Why's that? The marshalling is meant to be a backup for recovery or for role back to old version. If I have to reuse the old kBase this isn't possible, as the kBase will not always be available, e.g. when I restart my application and want to unmarshall the session from a file or database.

> Scheduled activations are rescheduled as if new when unmarshalling session in Drools 6.5
> ----------------------------------------------------------------------------------------
>
>                 Key: DROOLS-1537
>                 URL: https://issues.jboss.org/browse/DROOLS-1537
>             Project: Drools
>          Issue Type: Bug
>    Affects Versions: 6.5.0.Final
>            Reporter: Kay J
>            Assignee: Mario Fusco
>         Attachments: RestoreReproducer.java
>
>
> Ticket representing question/bug from drools user group: https://groups.google.com/forum/#!topic/drools-usage/Gy3uhkh6J78
> Hello Drools users,
> I found an anomaly in Drools 6.5. I insert an Event, which triggers a rule with a timer after some time. For backup reasons I marshal the session inbetween to back it up and on unmarshal it later. However, after unmarshalling it, the scheduled activations are sometimes scheduled as if just inserted (e.g. 1min scheduling, with marshal/unmarshal after 25s results in the activation firing after 85 (25+60) seconds instead of actual 60s. I know this worked with Drools 5.6 consistently, but now it sometimes works, sometimes not, which is indeterministic.
> I created a test reproducing this behaviour, which has changing output whenever you execute it. What the example does: It create a scheduled activation, which should trigger after 20s. After 10s the session is marshalled, destroyed and unmarshalled into a new session. After another 10s it should finally trigger. (10s + 10s -> the 20s scheduled).



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)