You could probably build a snapshot mechanism yourself. But I'd imagine it would get tricky if you have drools declared objects, and/or equality assert behavior, or you rely on the internal clock/time for any of your rules.

You would have to listen on the insert and retract callbacks, and maintain state separate from the drools session. Then have a background thread that wakes up and writes the snapshot. Reproducing the drools defined objects will be tricky, so you'll have to find a way to marshall these in and out. And you'll also have to keep track of the entry points the facts belong to so you know where to put them upon recovery.

Then when you start up, programmatically disable all the rules from firing, then insert the snapshot facts into their respective working memories, and then enable the rules. Or something like that :)

On Oct 7, 2013, at 7:13 AM, sirinath <sirinath1978m@gmail.com> wrote:

Regardless of single threaded or multi threaded it will be good if the engine has journaling and state persistence 

--
Suminda Sirinath Salpitikorala Dharmasena, B.Sc. Comp. & I.S. (Hon.) Lond., P.G.Dip. Ind. Maths. J'Pura, MIEEE, MACM ▣ Address: 6G • 1st Lane • Pagoda Road • Nugegoda 10250 • Sri Lanka. ▣ Mobile: +94-(0)711007945 ▣ Office: +94-(0) 11 2 199766 ▣ Home Office: +94-(0)11-5 875614 ▣ Home: +94-(0)11-5 864614 / 2 825908 ▣ Web: http://www.sakrio.com ▣
--


On 7 October 2013 16:21, jknehr [via Drools] <[hidden email]> wrote:
Boxbe jknehr [via Drools] ([hidden email]) is not on your Guest List | Approve sender | Approve domain

If your rules are deterministic (single threaded), this is easily accomplished by replaying the events into your session in the same order (so journal each event before inserting).

Although this is not a snapshot, it does allow you to rebuild state.

> On Oct 7, 2013, at 5:56 AM, sirinath <[hidden email]> wrote:
>
> Hi,
>
> Is it possible to have the ability to journal fact / rule / event
> submissions to the engine with the ability to save a snapshot.
>
> In case a error occurs you rollback to a previous point and play the events
> send to the engine.
>
> Also any error is easily reproducible.
>
> Suminda
>
>
>
> --
> View this message in context: http://drools.46999.n3.nabble.com/Journaling-and-Commit-Points-tp4026278.html
> Sent from the Drools: User forum mailing list archive at Nabble.com.
> _______________________________________________
> rules-users mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/rules-users

_______________________________________________
rules-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/rules-users


If you reply to this email, your message will be added to the discussion below:
http://drools.46999.n3.nabble.com/Journaling-and-Commit-Points-tp4026278p4026279.html
To unsubscribe from Journaling and Commit Points, click here.
NAML



View this message in context: Re: [rules-users] Journaling and Commit Points
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users