I'm having the same issue, but my reading of it is that it's the unique
constraint on the combination of processdefinition_ and key_ fields.
I don't get this behavior on hypersonic, but I do when I run against my Oracle
database.
View the original post :
http://www.jboss.com/index.html?module=
I created a JIRA entry on what I'm seeing:
http://jira.jboss.com/jira/browse/JBPM-913
I removed the unique constraint on key_ and processdefinition_, and that fixed
up my problem. I haven't done enough testing to confirm that it doesn't
*cause* other problems, however.
-Kevin
View the origina
"zipwow" wrote : I created a JIRA entry on what I'm seeing:
| http://jira.jboss.com/jira/browse/JBPM-913
|
| I removed the unique constraint on key_ and processdefinition_, and that
fixed up my problem. I haven't done enough testing to confirm that it doesn't
*cause* other problems, howev
I'd watch the JIRA for more details. Right now it says:
anonymous wrote : 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
constra
were either of you ever able to get this to work with MSSQL 2000 ?
I keep getting errors that it is a duplicate processID OR that it is trying to
insert "Null" into the processID field
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038182#4038182
Reply to th