[jboss-jira] [JBoss JIRA] (JGRP-2299) LockService does not work correctly if unlock/lock is called in immediate succession
Mirko Streckenbach (Jira)
issues at jboss.org
Wed Oct 3 02:50:00 EDT 2018
Mirko Streckenbach created JGRP-2299:
----------------------------------------
Summary: LockService does not work correctly if unlock/lock is called in immediate succession
Key: JGRP-2299
URL: https://issues.jboss.org/browse/JGRP-2299
Project: JGroups
Issue Type: Bug
Affects Versions: 4.0.15
Environment: Windows 10 Oracle JDK 1.8 131
AIX IBM Java 8
Reporter: Mirko Streckenbach
Assignee: Bela Ban
In our application we have encountered occasional cases of LockService allowing 2 processes to hold the same lock at the same time. I could reproduce this with a simple program (see atttachment) and it happens if for a lock "unlock" is called and immediately afterwards "lock". If there is a small delay (e.g. 1 second) between the two operations everything works as expected.
This can be produced with the attached program. The program does lock/unlock/lock on a lock and then tries to lock the same lock from a different JChannel and is awarded the lock. If you place a small sleep() after the unlock, everything works as expected and the parallel lock is not awarded.
If you turn on debugging you'll see no output between unlock and lock, so it looks to me like the lock is awarded without passing GRANT_EVENT to the stack. Using a conditional break point you can see that ClientLock.acquired is still true even after the unlock().
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
More information about the jboss-jira
mailing list