On 26/11/2010 15:16, Esteban Aliverti wrote:
Are you using the same session? Sessions are not thread-safe in drools.
Sessions should be thread safe, if they aren't its a bug. Most of the
methods locks while executing.
Looks like bug, something is blocking and not releasing.
Mark
Best,
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Esteban Aliverti
- Developer @ http://www.plugtree.com <http://www.plugtree.com>
- Blog @ http://ilesteban.wordpress.com
On Fri, Nov 26, 2010 at 12:12 PM, OptimusPrime <[email protected]
<mailto:[email protected]>> 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/StatefulKnowledgeSession-startProcess-not-thread-safe-tp1973203p1973203.html
Sent from the Drools - User mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
[email protected] <mailto:[email protected]>
https://lists.jboss.org/mailman/listinfo/rules-users
_______________________________________________
rules-users mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/rules-users
_______________________________________________
rules-users mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/rules-users
