On 02/09/2013, lalit2583 <lalit2583(a)gmail.com> wrote:
We are creating different StatefulKnowledge Session for different threads
all this StatefulKnowledgeSession are created from same KnowledgeBase,
KnowledgePackage. Is this an issue ?
It should not cause a problem. Synchronisation among user objects
(facts, globals) is user's burden.
You are correct the API doesnt tells
StatefuleKnowledgeSession is not thread safe. If I use
StatelessKnowledgeSession will it resolve the issue ?
Possibly: a Stateless KS is discarded after an execute, so you might appear
to avoid running into whatever caused your problem, but without
removing the cause.
But as per my knowledge internally StatelessKnowledgeSession uses
That's what the documentation says.
View this message in context:
Sent from the Drools: User forum mailing list archive at Nabble.com
rules-users mailing list