Thank you Santhosh,
Actually we already have the package building logic out of the session
execution stuff.
We will try to create directly a Stateful Session for each call as you did.
For now we are using our Stateless Session as a factory for the Stateful
(@see StatelessKnowledgeSessionImpl.execute(Object)). I'll update the post
with the results.
As a quick fix, we patched the JavaDialectRuntimeData class to synchronize
the loadClass(..) method. We didn't get any other concurrency problem (yet).
Regards,
--
View this message in context:
http://drools.46999.n3.nabble.com/rules-users-Concurrency-problem-in-Pack...
Sent from the Drools: User forum mailing list archive at
Nabble.com.