This discussion is archived
1 2 Previous Next 15 Replies Latest reply: Jul 26, 2012 6:42 AM by greybird Go to original post RSS
  • 15. Re: Deadlock found in je-5.0.48
    greybird Expert
    Currently Being Moderated
    Is there any possibility that this read lock it has is part of the same ReentrantReadWriteLock for which this same thread is trying to acquire the write lock? If so, that will definitely hang forever. That is, simply calling "lock.readLock().lock(); lock.writeLock().lock();" will block forever. See:
    According to our code this can't happen, since we never get a read lock on a BIN (latchShared always calls latchExclusive). But otherwise it would be something to suspect, especially given the null exclusive lock.sync.exclusiveOwnerThread field that Phil pointed out.

1 2 Previous Next


  • Correct Answers - 10 points
  • Helpful Answers - 5 points