[
https://issues.jboss.org/browse/JGRP-1912?page=com.atlassian.jira.plugin....
]
Chris Gentile updated JGRP-1912:
--------------------------------
Attachment: logFile2
Here is another run.
This run has a lock timeout of 60 seconds.
About 4 seconds into the test (test duration is two minutes), one of the 10 threads tries
to get a lock on one of the two items.
This attempt gets a timeout 60 seconds later, and the SEVERE message is recorded.
During the time that this thread is waiting, the other threads are continuing to acquire
and release locks on both items.
I don't think it matters how long the timeout is, this blocked thread is never going
to succeed on this tryLock() call.
After the timeout occurs, the thread continues normally to acquire and release locks on
both items.
LockService can fail under heavy load
-------------------------------------
Key: JGRP-1912
URL:
https://issues.jboss.org/browse/JGRP-1912
Project: JGroups
Issue Type: Bug
Affects Versions: 3.6.1
Environment: both windows 8.1 and RHEL
java 1.7.0_75
Reporter: Chris Gentile
Assignee: Bela Ban
Fix For: 3.6.3
Attachments: LockServiceTestClient.java, LockServiceTestClient.java, logFile,
logFile2, runLockServiceTestClient.sh, udp.xml
Once in awhile, the LockService will get stuck acquiring a lock.
These seems to occur most often when two threads are simultaneously trying to acquire the
same lock. (i.e.: exact same millisecond on a server with multiple processors).
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)