[jboss-jira] [JBoss JIRA] Assigned: (JBRULES-2837) StatefulKnowledgeSession.startProcess not thread-safe

[Mark Proctor (JIRA)]

     [ https://issues.jboss.org/browse/JBRULES-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Proctor reassigned JBRULES-2837:
-------------------------------------

    Assignee: Kris Verlaenen  (was: Mark Proctor)


> 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, 5.2.0.M1
>            Reporter: Maxence Dewil
>            Assignee: Kris Verlaenen
>
> See http://drools-java-rules-engine.46999.n3.nabble.com/StatefulKnowledgeSession-startProcess-not-thread-safe-td1973203.html
> and http://drools-java-rules-engine.46999.n3.nabble.com/Weird-Problem-WorkItemManager-seems-to-loose-WorkItems-td1986222.html
> The documentation lets believe that the StatefulKnowledgeSession can be used in a multithreaded environment (https://hudson.jboss.org/hudson/job/jBPM5/lastSuccessfulBuild/artifact/target/jbpm-5.0-SNAPSHOT-docs-build/jbpm-docs/html/ch04.html#d0e1191).
> 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