<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
The persistence mechanism for user provided objects is pluggable,
based on a given strategy. The reason for this is some people are
happy to have their objects serialised with the session state,
others have their objects in a DB somewhere and just want a
placeholder serialised. This works for process instance variables
and also inserted working memory facts.<br>
<br>
Mark<br>
On 20/02/2012 15:29, Mike Melton wrote:
<blockquote
cite="mid:CAAZ+K3_2BV2oAC=CPyeMcg5oYzDp=hknHRecg5NDiCYO7NFoaQ@mail.gmail.com"
type="cite">That's odd. We have stateful sessions persisted using
the techniques shown in the documentation you link to, and
rehydrated sessions are fully populated with all facts/events from
working memory as expected. We have the same requirement (sessions
must survive a server reboot 100% intact) and we have been quite
pleased with the results. The only things we have to re-establish
upon rehydration are globals and event listeners. We
use JPAKnowledgeService.newStatefulKnowledgeSession(..) to
establish new persisted sessions
and JPAKnowledgeService.loadStatefulKnowledgeSession(..) to
rehydrate existing persisted sessions.
<div>
<br>
</div>
<div>I doubt I've been much help to you but perhaps it will help
to know that someone has seen persistence work as advertised.</div>
<div><br>
</div>
<div>Mike<br>
<div><br>
<div class="gmail_quote">2012/2/20 Alberto R. Galdo <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:argaldo@gmail.com">argaldo@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
We are using Drools Expert, Fusion, Flow, etc... to
build a complex event processing system and one of our
main constraints is to be fault tolerant. As such, we are
using an StatefulKnowledgeSession and our system involves
processes, sets of rules, events, accumulators, ... . What
we need is to be able to reconstruct a KnowledgeSession in
a given state and all our changes in the knowledgesession
need to be persisted at the very moment a change is
detected.<br>
<br>
The documentation is sparse in this point ( <a
moz-do-not-send="true"
href="http://docs.jboss.org/drools/release/5.4.0.Beta2/drools-expert-docs/html/ch04.html#d0e2702"
target="_blank">http://docs.jboss.org/drools/release/5.4.0.Beta2/drools-expert-docs/html/ch04.html#d0e2702</a>
) and what we've seen so far is that our rules are
persisted but no traces of facts or events ... This would
be unaceptable for our product. We need to be able to stop
our service at any time and restore the knowledge session
at any time as it was at the moment of the previous stop.<br>
<br>
We have previous experience with JBPM 3 using a
persistent storage to be fault tolerant and it works like
a charm, we can see our processes, process instances,
timers, etc... . <br>
<br>
Can we get a *full* KnowledgeSession persistence
service for Drools?<br>
<br>
<br>
Greets,<br>
<br>
_______________________________________________<br>
rules-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
<a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/rules-users"
target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
rules-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/rules-users">https://lists.jboss.org/mailman/listinfo/rules-users</a>
</pre>
</blockquote>
<br>
</body>
</html>