[jboss-jira] [JBoss JIRA] Commented: (JBPM-913) ProcessBean.startInstance does not set ProcessInstance.key, causing second process start for any user to fail
[ http://jira.jboss.com/jira/browse/JBPM-913?page=comments#action_12358106 ]
David Lloyd commented on JBPM-913:
----------------------------------
The main issue here is that most databases (including mysql and oracle) do not index null
values (if you think about it, you'll see why). The appropriate workaround for your
case is probably to replace the unique constraint with a standard index on (KEY_,
PROCESSDEFINITION_).
The permanent fix is under discussion.
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: Tom Baeyens
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