[
https://issues.apache.org/jira/browse/GEODE-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572317#comment-16572317
]
ASF subversion and git services commented on GEODE-4928:
--------------------------------------------------------
Commit fcd6940600bc0ad3593a492c9a3a30bef4a9bf76 in geode's branch
refs/heads/develop from Dan Smith
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=fcd6940 ]
GEODE-5470: Deleting flaky DlockAndTxLockRegressionTest
This test was introduced as part of the fix for GEODE-4928. However,
we've determined that GEODE-4928 is not actually fixed, which is why
this test is sporadically failing.
Since GEODE-4928 actually appears to be trying to introduce new behavior
for dlocks that is a rather involved feature to implement. Leaving that
feature for another time and deleting this test.
> 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: New Feature
> Components: distributed lock service
> Reporter: Bruce Schuchardt
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 2.5h
> 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)
