Hello,
I've come around a bug in Activiti 5.14 when using an intermediate Timer Catch Event within a subProcess. When running such a simple process with H2 in Oracle compatibility mode Activiti crashes with a "Unique index or primary key violation" 'cause ACT_RU_EXECUTION(PROC_DEF_ID_, BUSINESS_KEY_) is not unique.
Note that this error does not occur when running in H2 native mode.
Details:
- Process: Simple process definition where the main process just starts a (embedded) sub process containing just an intermediate Timer Catch Event.
- Bug _occurs_, when using <property name="jdbcUrl" value="jdbc:h2:mem:activiti;MODE=Oracle;DB_CLOSE_DELAY=1000" /> in activiti.cfg.xml
- Bug _does not occur_ when using <property name="jdbcUrl" value="jdbc:h2:mem:activiti;DB_CLOSE_DELAY=1000" /> (i. e. running in H2 native mode)
Please see attached process definition, activity.cfg.xml and stack trace. I'd upload the whole unit test here, but only .txt is allowed. Additionally, I'm reporting this bug here since it seems to me that user registration at JIRA is disabled.
Kind regards,
Jörn
