[jboss-jira] [JBoss JIRA] (JGRP-1912) LockService can fail under heavy load

[Bela Ban (JIRA)]

    [ https://issues.jboss.org/browse/JGRP-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041779#comment-13041779 ] 

Bela Ban edited comment on JGRP-1912 at 2/19/15 6:14 AM:
---------------------------------------------------------

Why's {{CENTRAL_LOCK}} so far down in the stack ? That makes it unreliable, so {{GRANT_LOCK}} requests sent to the coordinator might simply get dropped and therefore a {{tryLock()}} could run into a timeout.

The documentation [1] recommends this (see last paragraph in 4.6).

[1] http://www.jgroups.org/manual/index.html#LockService


was (Author: belaban):
Why's {{CENTRAL_LOCK}} so far down in the stack ? That makes it unreliable, so {GRANT_LOCK} requests sent to the coordinator might simply get dropped and therefore a tryLock() could run into a timeout.

> 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)