[rules-users] Best approach for handling parallel requests for a stateful rules session

[Greg Barton]

They submit the commands to an execution queue, and they're executed in the order received in a thread safe manner.  And note there's an asyncFireAllRules() method, so you can time when rules fire.  As for whether objects are fed into working memory while rules are firing, I'm not sure, but that would be easy to test. (Just create rules that cause an infinite loop with low salience, start them up, and try to insert more data that trigger rules of a higher salience.)  Or maybe a dev will reply with a conclusive answer. :)

--- On Tue, 3/8/11, jkrupka <jkrupka at gmail.com> wrote:

> From: jkrupka <jkrupka at gmail.com>
> Subject: Re: [rules-users] Best approach for handling parallel requests for a stateful rules session
> To: rules-users at lists.jboss.org
> Date: Tuesday, March 8, 2011, 12:42 PM
> Took a look... thanks.  I'm not
> sure that they will help me though - do the
> async methods actually look to see if fireAllRules is
> already running
> somewhere else and synchronize the calls? Or do they just
> wrap a Callable
> around it so that if your rules take a long time to run you
> can do something
> else while they run?
> 
> --
> View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Best-approach-for-handling-parallel-requests-for-a-stateful-rules-session-tp2651617p2652011.html
> Sent from the Drools - User mailing list archive at
> Nabble.com.
> _______________________________________________
> rules-users mailing list
> rules-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
>