Re: [jgroups-users] questions about CENTRAL_LOCK locking service under 3.6.11

Questions/problems related to using JGroups <[email protected]> Fri, 13 Oct 2017 13:57:29 +0200
Newsgroups gmane.comp.java.javagroups.general
Message-ID <mailman.9927.1507895860.12861.javagroups-users@lists.sourceforge.net>

On 12/10/17 4:35 PM, Questions/problems related to using JGroups wrote:
> Ok a CENTRAL_LOCK -> unlockAll() JMX seemed to have worked even though an unlock on the coordinator at the _lock_ level did not work.  Maybe the unlock needs to happen from the same thread?

Yes! Exactly the same semantics as ReentrantLock. Alternatively, you 
could set

use_thread_id_for_lock_owner=true




>    What I'm confused about is that I'm always doing a try / finally with my locks and I'm not sure why I'm getting one stuck as locked.  This may indicate some other issue with general cluster communications.  Or maybe my applications are not properly shutting down and closing the locks?

Can you reproduce this?

>
> I've upgrade my master to 3.6.14 and we'll see if this reoccurs.  I've also added a custom log factory so I can dump logs to SLF4J so I'll be able to turn on trace logging in the future to see if I can see what's going on.

OK

>
> Thanks,
> gray
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> javagroups-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/javagroups-users

-- 
Bela Ban, JGroups lead (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