If you are trying to create a fail-over or a load-sharing system, you can also use a clustering toolkit like JGroups. JGroups is used with Tomcat for HttpSession clustering and JBoss for various clustering applications. Its also very stable.
Chintan
-----Original Message-----
From: Rich Halsey [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 27, 2004 6:43 AM
To: [EMAIL PROTECTED]
Subject: JESS: Re: 'mirroring' one jess process with another
This sounds like you are trying to create a "fail-over" system. Why don't
you just update the objects in the second system (from the first) and only
fire the rules when the second system is activated ?
----- Original Message -----
From: "amy" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 27, 2004 6:00 AM
Subject: JESS: 'mirroring' one jess process with another
>
> I have kind of a strange question; hope it makes sense.
>
> I would like to 'mirror' one Jess process with another by populating
> the second process-- perhaps progressively-- with information from the
> first. Then, I'd like to be able to stop the first process, tell the
> second one to run, and have it pick up where the first
> left off.
>
> Suppose I do NOT want to use bsave/bload for this.
> That is, I'd like an approach where I can effectively load 'declarative'
> information only, such as the rule and fact base (not the serialized
> runtime state) to create this 'mirror'.
>
> In general, it does not seem like this will work very well. Without
> maintaining the Rete net's refraction information from the first
> process, rules will fire 'again' in the 'mirror' process once its run
> cycle starts.
> (Of course it can be possible to alleviate some refiring issues by being
> careful with the rule & fact representation, but that gets tricky in
> general and I don't want to assume it).
>
> Perhaps one way to approach this is to configure the mirror process
> to run in a 'non-action' mode during the mirroring process -- that is,
> to
> 'fire' triggered rules WITHOUT executing their actions, as new facts
> are added to its fact base during mirroring, so as to keep its
> refraction information up to date.
> Does this seem like a feasible approach?
> Would it be a relatively straightforward modification to the
> Jess code on my part to support something like this?
>
> Alternatively, does anyone have any other suggestions for how to
> accomplish this kind of thing? (aside from "just use bsave" :).
>
> thanks,
> Amy
>
> --------------------------------------------------------------------
> To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
> in the BODY of a message to [EMAIL PROTECTED], NOT to the list
> (use your own address!) List problems? Notify [EMAIL PROTECTED]
> --------------------------------------------------------------------
>
>
--------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the list
(use your own address!) List problems? Notify [EMAIL PROTECTED]
--------------------------------------------------------------------
