DB2 and async deadlocks

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

acoliver

Getting deadlocks in many places on DB2 whenever there is anything async.  DB2 implemented optimistic locking, or something resembling it, a few releases ago but it works differently than Oracle/PostgreSQL/MSSQL(in Snapshot Isolation mode).  Can anyone confirm that the DB2 backend does not use this feature.  Do you suspect that if I alter it to use this feature that Activiti will work better? http://pic.dhe.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=%2Fcom.ibm.db2.luw.admin.dbobj.doc%2Fdoc%2Fr0051459.html and http://www.zinox.com/node/84

Has anyone else experienced this issue?

acoliver

In particular it pukes here:

<br>select&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; JOB.*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from ACT_RU_JOB JOB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LEFT OUTER JOIN ACT_RU_EXECUTION PI ON PI.ID_ = JOB.PROCESS_INSTANCE_ID_&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LEFT OUTER JOIN ACT_RE_PROCDEF PD ON PD.ID_ = PI.PROC_DEF_ID_&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; where (JOB.RETRIES_ > 0)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and (JOB.DUEDATE_ is null or JOB.DUEDATE_ < ?)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and (JOB.LOCK_OWNER_ is null or JOB.LOCK_EXP_TIME_ < ?)&nbsp;&nbsp;&nbsp; and (&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (JOB.EXECUTION_ID_ is null)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; or ((PI.SUSPENSION_STATE_ = 1)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and (PD.SUSPENSION_STATE_ = 1))&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; )<br>