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

[Architect SoftWeb.ISD (JIRA)]

     [ https://issues.jboss.org/browse/JGRP-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Architect SoftWeb.ISD updated JGRP-1679:
----------------------------------------

    Attachment: lockservice_stability_testcase.jar


lockservice_stability_testcase.jar attachment is added.
It is test.
The test is hardcoded to work during 5 minutes with 20 threads.
Java source is inside of the attachment.

Windows command line:
\jdk1.6.0_31\jre\bin\java.exe -cp junit-4.4.jar;jgroups-3.2.4.Final.jar;log4j-1.2.15.jar;lockservice_stability_testcase.jar org.junit.runner.JUnitCore com.softcomputer.softweb.infl.commons.clustering.stabilitytest.LockServiceStabilityTestCase

Dependencies:
jgroups-3.2.4.Final.jar (with jgroups-3.3.4.Final the situation is the same)
junit-4.4.jar
log4j-1.2.15.jar (log4j.xml is inside. It creates test.trace file)
                
> tryLock with 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
>         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