[
https://issues.apache.org/jira/browse/GEODE-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16414171#comment-16414171
]
ASF subversion and git services commented on GEODE-4928:
--------------------------------------------------------
Commit 3c65d9b296569cc2a769187881ab14c6fe3c9a93 in geode's branch
refs/heads/feature/GEODE-4928b from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3c65d9b ]
GEODE-4928 DistributedLockService doesn't work as expected while the dlock
grantor is initialized
Moved setting of the in-process state to a point before we launch the
background thread to do the cleanup. Added in-line cleanup with a warning
message if background execution is rejected and we aren't shutting down.
If we _are_ shutting down the in-process state is left being set to true
so that lockers won't get a spurious conflict exception from the grantor
and will retry their commits with a new grantor when one is created.
> DistributedLockService doesn't work as expected while the dlock grantor is
> initialized
> --------------------------------------------------------------------------------------
>
> Key: GEODE-4928
> URL: https://issues.apache.org/jira/browse/GEODE-4928
> Project: Geode
> Issue Type: Bug
> Components: distributed lock service
> Reporter: Bruce Schuchardt
> Assignee: Bruce Schuchardt
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> I wrote a function that obtained a dlock and then performed a transaction.
> It always operates on the same dlock key and the same keys in my region.
> That protects against getting a commit conflict exception BUT this sometimes
> fails if the JVM holding the lock crashes. One of the functions appears to
> get the dlock okay but then its transaction fails when it goes to commit.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
