Description of problem:
We are experiencing problems due to a lock on JBPM DB. We persist JBPM on Oracle 18.104.22.168.0.
The problem may be related to a missing index, we added the following index:
# the foreign key constraint (already present in jBPM ddl script):
alter table JBPM_TASKINSTANCE add constraint FK_TSKINS_PRCINS foreign key (PROCINST_) references JBPM_PROCESSINSTANCE;
# new index to add to the schema:
create index IDX_TASKINST_PRCINS on JBPM_TASKINSTANCE (PROCINST_);
Added the index, but the way they word the problem makes me curious as to whether or not this actually was the solution (for them):
"The problem may be related to a missing index" (emphasis on may.. ).
However, knowing jBPM 3 and it's DB schema, I wouldn't be all that surprised.
Verified in SOA-P-5.3.1.ER4