... leading to the second
problem.
I guess we need to re-tests the second problem after the first is fixed.
-Original Message-
From: aealexsandrov [mailto:aealexsand...@gmail.com]
Sent: 28 June 2018 08:02
To: user@ignite.apache.org
Subject: Re: Problems with unlocking multiply held cache locks
Andrew,
The issue, that you filed, shows a different problem. It doesn't address
lock's reentrancy.
Lock's implementation contains a counter, that tracks, how many times it
was acquired.
But it's ignored in the *unlock()* method.
So, I think, the lock shouldn't be released, until the *unlock()*
Hi,
As I remember we already discussed here with Jon:
http://apache-ignite-users.70518.x6.nabble.com/If-a-lock-is-held-by-another-node-IgniteCache-isLocalLocked-appears-to-return-incorrect-results-td22110.html#a22149
that isLocalLocked method works incorrectly in case if several nodes started
, or not release the cache lock
until it's unlocked the corresponding number of times.
Initial post:
http://apache-ignite-users.70518.x6.nabble.com/Problems-with-unlocking-multiply-held-cache-locks-td22317.html
Denis
ср, 27 июн. 2018 г. в 17:00, Jon Tricker :
> It appears that cache locks are inten
It appears that cache locks are intended to support re-entrancy. The debugger
shows a count variable and the lock can be taken several times by the same node
and then unlocked an equal number of times.
If a node has taken a lock several times a second node attempts to take the
same lock then,
