Bug 866926 - Create index for the foreign key constraint on the JBPM_TASKINSTANCE.PROCINST_ column
Summary: Create index for the foreign key constraint on the JBPM_TASKINSTANCE.PROCINST...
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBPM - standalone, JBPM - within SOA
Version: 5.3.0 GA
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ER4
: 5.3.1
Assignee: Shelly McGowan
QA Contact: Ivo Bek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-16 10:41 UTC by Martin Weiler
Modified: 2018-11-29 19:45 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Users have been experiencing deadlocks in JBPM due to a missing index. Deadlocks are now avoided with the addition of a new index according to the following: # 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_);
Clone Of:
Environment:
Last Closed:
Type: Task


Attachments (Terms of Use)

Description Martin Weiler 2012-10-16 10:41:24 UTC
Description of problem:
We are experiencing problems due to a lock on JBPM DB. We persist JBPM on Oracle 11.2.0.2.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_);

Comment 2 Marco Rietveld 2012-12-06 11:30:29 UTC
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.

Comment 3 Ivo Bek 2013-02-01 09:24:59 UTC
Verified in SOA-P-5.3.1.ER4


Note You need to log in before you can comment on or make changes to this bug.