I’m not sure I understand the question.
You have two totally independent rule engine on two different servers running with separate JVMs and sessions.
You happen to share data between the two sessions by updating a database but drools has no knowledge of that (they are just java objects which happen to exist)
and they certainly aren’t the same object on both servers.
Temporal reasoning and correlation of events will therefore only happen on the facts that are inserted into that processes working memory – there’s no way it
could be any way else as it only know about itself, there could be 10 or 0 other processes running it won’t know the difference.
The ideal method is to have an application design where each request is totally independent from all other requests (other than db state) and therefore you
do exactly as you have described – there is no other state to share. If you have to share state between them you have a much bigger problem and you probably have to find some other way to partition up the data into separate blocks.
Thomas
From: rules-users-bounces@lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org]
On Behalf Of Neelesh Deo Dani
Sent: 02 August 2011 07:42
To: rules-users@lists.jboss.org
Subject: [rules-users] running multiple instance of rule engine
|