geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (Jira)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-7087) IllegalMonitorStateException: attempt to unlock read lock, not locked by current thread is shown in debug logging
Date Wed, 04 Sep 2019 19:05:00 GMT

    [ https://issues.apache.org/jira/browse/GEODE-7087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16922763#comment-16922763
] 

ASF subversion and git services commented on GEODE-7087:
--------------------------------------------------------

Commit 4022b8cf3f8c99ff51bf8baef65a4f1c86fd74ba in geode's branch refs/heads/develop from
eshu
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4022b8c ]

Revert "GEODE-7087: Reset flag after unlock bucket primary lock. (#3926)"

This reverts commit b5c0395218822eb6fc2881634f7d9cd80560a4d7.


> IllegalMonitorStateException: attempt to unlock read lock, not locked by current thread
is shown in debug logging
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-7087
>                 URL: https://issues.apache.org/jira/browse/GEODE-7087
>             Project: Geode
>          Issue Type: Bug
>          Components: transactions
>            Reporter: Eric Shu
>            Assignee: Eric Shu
>            Priority: Major
>              Labels: GeodeCommons
>             Fix For: 1.11.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> GotBucketLocks flag is never being reset after lock is released cause the following debug
logging. However. it does not affect the correctness of the transaction layer.
> [vm3] [debug 2019/08/14 05:14:37.163 PDT <ServerConnection on port 64115 Thread 13>
tid=0x5464] Exception while unlocking bucket region /_PR/_BClientServerTransactionFailoverDistributedTestmultipleClientLongTransactionsCanFailoverWithoutLosingOperations_region_0
this is probably because the bucket was destroyed and never locked initially.
> [vm3] java.lang.IllegalMonitorStateException: attempt to unlock read lock, not locked
by current thread
> [vm3] at java.util.concurrent.locks.ReentrantReadWriteLock$Sync.unmatchedUnlockException(ReentrantReadWriteLock.java:444)
> [vm3] at java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:428)
> [vm3] at java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1341)
> [vm3] at java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:881)
> [vm3] at org.apache.geode.internal.cache.BucketRegion.doUnlockForPrimary(BucketRegion.java:862)
> [vm3] at org.apache.geode.internal.cache.TXState.doCleanup(TXState.java:913)
> [vm3] at org.apache.geode.internal.cache.TXState.cleanup(TXState.java:880)
> [vm3] at org.apache.geode.internal.cache.TXManagerImpl.cleanupTransactionIfNoLongerHost(TXManagerImpl.java:1069)
> [vm3] at org.apache.geode.internal.cache.TXManagerImpl.unmasquerade(TXManagerImpl.java:1055)
> [vm3] at org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:180)
> [vm3] at org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMessage(ServerConnection.java:848)
> [vm3] at org.apache.geode.internal.cache.tier.sockets.OriginalServerConnection.doOneMessage(OriginalServerConnection.java:72)
> [vm3] at org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1212)
> [vm3] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [vm3] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [vm3] at org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.lambda$initializeServerConnectionThreadPool$3(AcceptorImpl.java:673)
> [vm3] at org.apache.geode.internal.logging.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:121)
> [vm3] at java.lang.Thread.run(Thread.java:748)



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Mime
View raw message