0 Replies Latest reply on Mar 23, 2006 5:45 PM by Pravin kamble

    JBPM Database Deadlock problem

    Pravin kamble Newbie

      DEADLOCK DETECTED

      Current SQL statement for this session:

      update JBPM_TOKEN set NAME_=:1, START_=:2, END_=:3, NODEENTER_=:4, NEXTLOGINDEX_=:5, ISABLETOREACTIVATEPARENT_=:6, ISTERMINATIONIMPLICIT_=:7, NODE_=:8, PROCESSINSTANCE_=:9, PARENT_=:10 where ID_=:11

      The following deadlock is not an ORACLE error. It is a

      deadlock due to user error in the design of an application

      or from issuing incorrect ad-hoc SQL. The following

      information may aid in determining the deadlock:

      Deadlock graph:

      ---------Blocker(s)-------- ---------Waiter(s)---------

      Resource Name process session holds waits process session holds waits

      TM-0000258e-00000000 14 22 SX 13 27 SX SSX

      TX-0007001a-0000612e 13 27 X 14 22 X

      session 22: DID 0001-000E-00001106 session 27: DID 0001-000D-00002EA8

      session 27: DID 0001-000D-00002EA8 session 22: DID 0001-000E-00001106

      Rows waited on:

      Session 27: obj - rowid = 00002596 - AAACWWAAQAAAAAAAAA

      (dictionary objn - 9622, file - 16, block - 0, slot - 0)

      Session 22: obj - rowid = 0000258E - AAACWOAAQAAAAMGABc

      (dictionary objn - 9614, file - 16, block - 774, slot - 92)

      Information on the OTHER waiting sessions:

      Session 27:

      pid=13 serial=55637 audsid=738276 user: 99/COMWFLSVC

      O/S info: user: jbsadmin, term: unknown, ospid: , machine: s0161cdc

      program: JDBC Thin Client

      application name: JDBC Thin Client, hash value=0

      Current SQL Statement:

      delete from JBPM_PROCESSINSTANCE where ID_=:1

      End of information on OTHER waiting sessions.

      Changing data in table JBPM_TOKEN will lock table JBPM_PROCESSINSTANCE