[jboss-jira] [JBoss JIRA] Closed: (JBPM-913) ProcessBean.startInstance does not set ProcessInstance.key, causing second process start for any user to fail

[David Lloyd (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBPM-913?page=all ]

David Lloyd closed JBPM-913.
----------------------------

    Fix Version/s:  jBPM jPDL 3.2.1
       Resolution: Done
         Assignee: David Lloyd  (was: Tom Baeyens)

Replaced unique constraint with a plain index.  A unique constraint can still be added provided that the criteria above are met - that is, the indexed column(s) must be all null if the key is null.

> ProcessBean.startInstance does not set ProcessInstance.key, causing second process start for any user to fail
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPM-913
>                 URL: http://jira.jboss.com/jira/browse/JBPM-913
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Web Interface
>    Affects Versions: jBPM jPDL 3.2
>            Reporter: Kevin Klinemeier
>         Assigned To: David Lloyd
>             Fix For:  jBPM jPDL 3.2.1
>
>
> The web console isn't setting the ProcessInstance.key value.  This value has a unique constraint across key_ and processdefinition_
> To reproduce, either:
>  run against a non-hypersonic database and attempt to create two process instances for any one process definition.
> or 
>  run against  hypersonic, writing data to a file.  Inspect Process_Instances to see constraint violated by null, which apparently isn't caught by hypersonic.
> It's not clear to me how to correctly populate this field.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira