[
https://issues.jboss.org/browse/JBRULES-2837?page=com.atlassian.jira.plug...
]
Maxence Dewil edited comment on JBRULES-2837 at 2/21/11 12:03 PM:
------------------------------------------------------------------
Still not fixed in JBPM 5.0 and Drools 5.2.0.M1
was (Author: maxence.dewil):
Ok this one is fixed in Drools 5.2.0.M1
StatefulKnowledgeSession.startProcess not thread-safe
-----------------------------------------------------
Key: JBRULES-2837
URL:
https://issues.jboss.org/browse/JBRULES-2837
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core
Affects Versions: 5.1.1.FINAL
Reporter: Maxence Dewil
Assignee: Mark Proctor
See
http://drools-java-rules-engine.46999.n3.nabble.com/StatefulKnowledgeSess...
and
http://drools-java-rules-engine.46999.n3.nabble.com/Weird-Problem-WorkIte...
The documentation lets believe that the StatefulKnowledgeSession can be used in a
multithreaded environment
(
https://hudson.jboss.org/hudson/job/jBPM5/lastSuccessfulBuild/artifact/ta...).
But the classes org.drools.process.instance.impl.DefaultProcessInstanceManager and
org.drools.process.instance.impl.DefaultWorkItemManager are not synchronized.
Consequences: process instance ids and workitem ids not unique.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira