• Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 1.6.1, 2.0
    • Fix Version/s: 1.6.2, 2.1
    • Component/s: jackrabbit-core
    • Labels:
    • Environment:
      Weblogic 9.2


      In one of our client deployments on WebLogic 9.2 we observed JackRabbit sessions going stale in a load test. This was observed against release 1.6.1 (to which we migrated due to concurrency related issues JCR-2081 and JCR-2237). Same effect with 2.0.0.

      I could finally reproduce this issue locally. And it seems to boil down to WLS invoking the sequence of <prepare> ... <release> ... <commit> on one XA session from multiple threads, as it seems breaking assumptions of the thread-bound java.util.concurrent-RWLock based DefaultISMLocking class.
      Effectively the setActiveXid(..) method on DefaultISMLocking$RWLock fails as the old active XID was not yet cleared. With the result of more and more sessions deadlocking in below's invocation stack.

      "[ACTIVE] ExecuteThread: '27' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=1 tid=0x33fc3ec0 nid=0x2324 in Object.wait() [0x2156a000..0x2156beb0] at java.lang.Object.wait(Native Method) - waiting on <0x68a54698> (a EDU.oswego.cs.dl.util.concurrent.WriterPreferenceReadWriteLock$WriterLock) at java.lang.Object.wait( at EDU.oswego.cs.dl.util.concurrent.WriterPreferenceReadWriteLock$WriterLock.acquire(Unknown Source) - locked <0x68a54698> (a EDU.oswego.cs.dl.util.concurrent.WriterPreferenceReadWriteLock$WriterLock) at org.apache.jackrabbit.core.state.DefaultISMLocking$1.<init>( at org.apache.jackrabbit.core.state.DefaultISMLocking.acquireWriteLock( at org.apache.jackrabbit.core.version.AbstractVersionManager.acquireWriteLock( at org.apache.jackrabbit.core.version.XAVersionManager$1.prepare( at org.apache.jackrabbit.core.TransactionContext.prepare( - locked <0x6dc2ad88> (a org.apache.jackrabbit.core.TransactionContext) at org.apache.jackrabbit.core.XASessionImpl.prepare( at org.apache.jackrabbit.jca.TransactionBoundXAResource.prepare( at at weblogic.connector.transaction.outbound.XAWrapper.prepare( at weblogic.transaction.internal.XAServerResourceInfo.prepare( at weblogic.transaction.internal.XAServerResourceInfo.prepare( at weblogic.transaction.internal.ServerSCInfo$1.execute( at weblogic.kernel.Kernel.executeIfIdle( at weblogic.transaction.internal.ServerSCInfo.startPrepare( at weblogic.transaction.internal.ServerTransactionImpl.localPrepare( at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare( at weblogic.transaction.internal.ServerTransactionImpl.internalCommit( at weblogic.transaction.internal.ServerTransactionImpl.commit( at weblogic.transaction.internal.TransactionManagerImpl.commit( at org.springframework.transaction.jta.JtaTransactionManager.doCommit( at at


        1. Xid.patch
          3 kB
          Claus Köll
        2. Xid_v4.patch
          12 kB
          Claus Köll
        3. Xid_v3.patch
          5 kB
          Claus Köll
        4. Xid_v2 deadlock.jpg
          62 kB
          Robert Sauer
        5. Xid_v2 + SynchronizedRef for markedXid.jpg
          63 kB
          Robert Sauer
        6. Xid_v2.patch
          5 kB
          Claus Köll
        7. LockManager.patch
          4 kB
          Claus Köll
        8. jr-core-xid-aware-ism-locking1.patch
          16 kB
          Robert Sauer
          5 kB
          Robert Sauer



            • Assignee:
              c_koell Claus Köll
              rsauer Robert Sauer
            • Votes:
              0 Vote for this issue
              1 Start watching this issue


              • Created: