LockNotPendingError: Attempt to reject a lock request that isn’t pending

Type: Bug
Status: Closed
Priority: 2 Major
Resolution: Fixed
Component/s: DSO:L1
Labels:

Assignee: nadeem
Reporter: teck
Created: June 25, 2008
Votes: 0
Watchers: 0
Updated:
September 24, 2008
Resolved:
July 10, 2008

Description

MultiNodeInvalidatorTest fails fairly regularly because the L1s exit with this assertion error

com.tc.object.lockmanager.api.LockNotPendingError: Attempt to reject a lock request that isn’t pending: lockID: LockID(D540816D200CA69D05EEA7C8750978970808F6A9D90AA0B12625), level: 2, requesterID: ThreadID=[7], waitLocksByRequesterID: {} at com.tc.object.lockmanager.impl.ClientLock.cannotAwardLock(ClientLock.java:466) at com.tc.object.lockmanager.impl.ClientLockManagerImpl.cannotAwardLock(ClientLockManagerImpl.java:483) at com.tc.object.handler.LockResponseHandler.handleEvent(LockResponseHandler.java:43) at com.tc.async.impl.StageImpl$WorkerThread.run(StageImpl.java:142)

I’m almost certain this problem has something to do with the tryLock() APIs. TC sessions makes pretty heavy use of this API, and anyone who uses tryLock() on ReentrantLock and/or ReentrantReadWriteLock() could be affected by this bug

this is probably the same thing as CDV-649

Comments

Tim Eck 2008-07-10

this should be resolved with Geert’s fixes for tryLock(). Test is re-enabled

Fiona OShea 2008-08-14

The test passing should be verification enough for this…2.6.3

nadeem ghani 2008-08-15

closing because this test is passing now