move deadlock
-------------

                 Key: JCR-2131
                 URL: https://issues.apache.org/jira/browse/JCR-2131
             Project: Jackrabbit Content Repository
          Issue Type: Bug
          Components: jackrabbit-core
         Environment: Linux
            Reporter: Lorenzo Pavesi


during concurrent workspace move in cluster jackrabbit environment i
get a deadlock, (moving different node from different source to the
same destination directory). I get the same problem using also the session move.

Follow a stack trace:

Thread [DefaultQuartzScheduler_Worker-3] (Suspended)
    Object.wait(long) line: not available [native method] [local variables 
unavailable]
    WriterPreferenceReadWriteLock$ReaderLock(Object).wait() line: 485 [local 
variables unavailable]
    WriterPreferenceReadWriteLock$ReaderLock.acquire() line: not available 
[local variables unavailable]
    DefaultISMLocking$ReadLockImpl.<init>(Sync) line: 78
    DefaultISMLocking$ReadLockImpl.<init>(Sync, DefaultISMLocking$1) line:72
    DefaultISMLocking.acquireReadLock(ItemId) line: 40
    SharedItemStateManager.acquireReadLock(ItemId) line: 1401
    SharedItemStateManager.hasItemState(ItemId) line: 279
    XAItemStateManager.hasItemState(ItemId) line: 288
    SessionItemStateManager.hasItemState(ItemId) line: 206
    CachingHierarchyManager(HierarchyManagerImpl).hasItemState(ItemId) line:164
    CachingHierarchyManager.nodeRemoved(NodeState, Path, NodeId) line:725
    CachingHierarchyManager.nodeRemoved(NodeState, Name, int, NodeId) line:455
    StateChangeDispatcher.notifyNodeRemoved(NodeState, Name, int, NodeId)line: 
157
    SessionItemStateManager.nodeRemoved(NodeState, Name, int, NodeId) line:941
    NodeState.notifyNodeRemoved(ChildNodeEntry) line: 871
    NodeState.removeChildNodeEntry(Name, int) line: 388
    XASessionImpl(SessionImpl).move(String, String) line: 1035
    Worker.execute(JobExecutionContext) line: 121
    Worker.run() line: 202
    SimpleThreadPool$WorkerThread.run() line: 525 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to