[ https://issues.jboss.org/browse/JGRP-2299?page=com.atlassian.jira.plugin.... ] David White edited comment on JGRP-2299 at 8/20/19 6:40 PM: ------------------------------------------------------------ I tried to test this fix (4.1.2) but unfortunately something seems to be broken with the CENTRAL_LOCK2 protocol. Upon shutdown, my application successfully closes the JChannel which uses the CENTRAL_LOCK2 protocol. However, after the application completely exits from all my application code the JVM is still running and never exits. It appears there is a thread still running the CENTRAL_LOCK2 protocol and it is stuck in the method processQueue() on the line "req=req_queue.take();}. The last version I tested was 4.0.19 so I don't know when this problem was introduced. Please advise. was (Author: dwhitejazz): I tried to test this fix (4.1.2) but unfortunately something seems to be broken with the CENTRAL_LOCK2 protocol. Upon shutdown, my application successfully closes the JChannel which uses the CENTRAL_LOCK2 protocol. However, after the application completely exits from all my application code the JVM is still running and never exits. It appears there is a thread still running the CENTRAL_LOCK2 protocol and it is stuck in the method processQueue() on the line "req=req_queue.take();}. The last version I tested was 4.0.19 so I don't know when this problem was introduced. Please advise. Dave From: "Bela Ban (Jira)" <issues(a)jboss.org&gt; To: dfwhite(a)us.ibm.com Date: 08/02/2019 08:25 AM Subject: [EXTERNAL] [JBoss JIRA] (JGRP-2299) LockService does not work correctly if unlock/lock is called in immediate succession Bela Ban resolved as Done Resolving this; let me know if this fixes all of your issues! JGroups / JGRP-2299 LockService does not work correctly if unlock/lock is called in immediate succession Change By: Bela Ban Status: Open Resolved Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.12.1#712002-sha1:609a505) -- This message was sent by Atlassian Jira (v7.12.1#712002)