Are you using the same session? Sessions are not thread-safe in drools. Best, XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Esteban Aliverti - Developer @ http://www.plugtree.com - Blog @ http://ilesteban.wordpress.com On Fri, Nov 26, 2010 at 12:12 PM, OptimusPrime <the.maxxxx(a)gmail.com&gt; wrote:

org.drools.StatefulSession has the async* methods, which are thread safe.  I'm not sure if org.drools.runtime.StatefulKnowledgeSession.execute(Command<T> command) uses them behind the scenes, though. --- On Fri, 11/26/10, Wolfgang Laun <wolfgang.laun(a)gmail.com&gt; wrote: From: Wolfgang Laun <wolfgang.laun(a)gmail.com&gt; Subject: Re: [rules-users] StatefulKnowledgeSession.startProcess not thread-safe ? To: "Rules Users List" <rules-users(a)lists.jboss.org&gt; Date: Friday, November 26, 2010, 9:33 AM 2010/11/26 Esteban Aliverti <esteban.aliverti(a)gmail.com&gt; Are you using the same session? Sessions are not thread-safe in drools. Sessions not thread-safe? So how do I run x.fireUntilHalt() in one session and do insert() in other threads? Do I have to synchronize this myself? -W  Best,  XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Esteban Aliverti - Developer @ http://www.plugtree.com - Blog @ http://ilesteban.wordpress.com On Fri, Nov 26, 2010 at 12:12 PM, OptimusPrime <the.maxxxx(a)gmail.com&gt; wrote: Hello, I wrote a micro benchmark in order to test the performance of Drools Flow 5.1.0 in single and multi-threaded environments. And I noticed that, when 2 threads call startProcess() at the same time (Intel Core 2 Duo CPU), the returned process instance IDs are the same. I checked the code and it seems there is no locking mechanism in the org.drools.process.instance.impl.DefaultProcessInstanceManager class for the id creation. Is this a bug or am I missing something ? Thanks -- View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/StatefulKnowledgeSess... Sent from the Drools - User mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users -----Inline Attachment Follows----- _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

I changed the DefaultProcessInstanceManager class to make it thread-safe. The file drools.session.conf should be placed in the classpath, under META-INF. http://drools-java-rules-engine.46999.n3.nabble.com/file/n1985449/drools.... drools.session.conf http://drools-java-rules-engine.46999.n3.nabble.com/file/n1985449/ThreadS... ThreadSafeProcessInstanceManager.java http://drools-java-rules-engine.46999.n3.nabble.com/file/n1985449/ThreadS... ThreadSafeProcessInstanceManagerFactory.java -- View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/StatefulKnowledgeSess... Sent from the Drools - User mailing list archive at Nabble.com.

There are more unsafe methods: I got locks when calling completeWorkItem, fireAllRules and insert concurrently. juergen -- View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/StatefulKnowledgeSess... Sent from the Drools - User mailing list archive at Nabble.com.