[
http://jira.jboss.com/jira/browse/JBCACHE-1165?page=all ]
Jacek Halat updated JBCACHE-1165:
---------------------------------
Attachment: ConcurentPutRemoveTest.java
ConsoleOut.log
JUnit test to this issue.
This test sometimes finish with success, sometimes fails with NodeNotExistException and
sometimes goes into infinitive loop.
Attached ConsoleOutput with ThreadDumps when test goes into infinivie loop.
Endless loop in PessimisticLockInterceptor
------------------------------------------
Key: JBCACHE-1165
URL:
http://jira.jboss.com/jira/browse/JBCACHE-1165
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.4.1.SP4
Environment: Windows XP, Sun jdk150_06
Solaris 10
Reporter: Jacek Halat
Assigned To: Manik Surtani
Attachments: ConcurentPutRemoveTest.java, ConsoleOut.log
When 2 Threads are simulatanous putting/removing values from this same node TreeCache
hang's up and goes into endless loop.
Main loop looks like:
for (int x = 0; x < 1000; x++) {
tm.begin();
System.out.println("R" + Thread.currentThread().getName());
//inside transaction
cache.remove("/a");
System.out.println("AR" + Thread.currentThread().getName());
tm.commit();
//outside transaction
System.out.println("P" + Thread.currentThread().getName());
cache.put("/a/b/c/d", "text"+x,"b");
System.out.println("AP" + Thread.currentThread().getName());
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira