Re: [jgroups-users] Locks get locked forever after a cluster members leaves
Questions/problems related to using JGroups <[email protected]> Mon, 23 Oct 2017 15:15:45 +0200
| Newsgroups | gmane.comp.java.javagroups.general |
|---|---|
| Message-ID | <mailman.16352.1508764554.14213.javagroups-users@lists.sourceforge.net> |
On 23/10/17 15:05, Questions/problems related to using JGroups via
javagroups-users wrote:
>> What do you mean? You must have called Lock.lock(), right? Below you
>> mention that all lock() calls are changed into corresponding tryLock()
>> calls, but the output you showed clearly indicate that the queue has a
>> regular lock() request by 373 pending, followed by a tryLock() request...
>
> I need some more time to reply to your first response but this one is
> easy. I *never* use a regular lock() call on the JGroups lock (I wrap
> them, see example), the only calls done on the JGroups lock are
> tryLock(..) calls.
Well, why am I seeing a regular lock() request in the queue then (see
the first queue element below)?
queue:
L(writelock/regular/instance_2_1/,40388::373)
TL(writelock/regular/instance_2_1/,45507::413,20000)
The first queued lock request is clearly a Request for a lock() , *not*
a tryLock()!
-
Bela Ban | http://www.jgroups.org
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot