Continuation of a process after a system crash/restart - Drools Flow -
i've been playing examples downloaded book drools jboss rules 5.0. relief work :) drools flow has been point of interest possible workflow engine replacement.
as i'm trying wrap head around things, i've been wondering how premature death of rulesflow process gets restarted? i'm mean process bouncing 1 node expected, containing process dies due crash, restart or whatever. current node/place of ruleflow process retained, , can continue point on system restart? if how?
the group work java ee centric jboss being our favorite application server. see examples of drools leveraging spring's persistence , bean lookup support.
are there examples of doing same jboss?
if persist state of process instances , tasks in database. if vm down , restart again, can retrieve process instances.
use
to create session
ksession = jpaknowledgeservice.newstatefulknowledgesession(kbase,null,env)
to load session session id.
ksession = jpaknowledgeservice.loadstatefulknowledgesession( sessionid, kbase,
you need know session id. session information store in sessioninfo table. download example project below.
http://dl.dropbox.com/u/2634115/drools-test.zip
the example using btm h2 database, work mysql-connector-java-5.1.13 btm. note process complete automatically deleted database.
Comments
Post a Comment