[jboss-jira] [JBoss JIRA] (JGRP-1679) tryLock with (and without) timeout allows simultaneous concurrent access to not thread-safe data to more then one client

[Bela Ban (JIRA)]

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

Bela Ban commented on JGRP-1679:
--------------------------------

Similar things can happen for spurious LOCK-DENIED responses; if a lock was granted and we get a LOCK-DENIED response, the lock will be denied although it was actually granted !
                
> tryLock with (and without) timeout allows simultaneous concurrent access to not thread-safe data to more then one client
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JGRP-1679
>                 URL: https://issues.jboss.org/browse/JGRP-1679
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 3.2.4, 3.3.4
>         Environment: Intel(R) Core(TM) i5-2310 CPU @ 2.90GHz 
> 8 GB RAM 
> Windows 7 
> JRE 1.6.31
>            Reporter: Architect SoftWeb.ISD
>            Assignee: Bela Ban
>             Fix For: 3.4
>
>         Attachments: lockservice_stability_testcase.jar
>
>
> It looks as it is possible to access a not thread-safe data simultaneously by several clients when tryLock with timeout is used.
> It is reproduced easily with timeouts from 1 to 3 seconds inclusive.
> It is very difficult to reproduce the issue with bigger values of the timeout.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira