[
https://issues.jboss.org/browse/JGRP-1912?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1912:
--------------------------------
Item range=2 and lock-duration=0 works for me.
What exactly do you see as a failure ? Not being able to acquire a lock ? That's
entirely possible as the lock queue of the server might become filled, so tryLock()
requests take longer than 2s.
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.2
Attachments: LockServiceTestClient.java
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)