2:34 a.m.
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
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
2:38 a.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-1165) Endless loop in PessimisticLockInterceptor
[ 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
10:38 a.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-1165) Endless loop in PessimisticLockInterceptor
[ http://jira.jboss.com/jira/browse/JBCACHE-1165?page=all ]
Manik Surtani updated JBCACHE-1165:
-----------------------------------
Fix Version/s: 1.4.1.SP5
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
Fix For: 1.4.1.SP5
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
7:54 a.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-1165) Endless loop in PessimisticLockInterceptor
[ http://jira.jboss.com/jira/browse/JBCACHE-1165?page=all ]
Manik Surtani updated JBCACHE-1165:
-----------------------------------
Fix Version/s: 2.1.0.GA
Affects Version/s: 2.0.0.GA
Complexity: High
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: 2.0.0.GA, 1.4.1.SP4
Environment: Windows XP, Sun jdk150_06
Solaris 10
Reporter: Jacek Halat
Assigned To: Manik Surtani
Fix For: 2.1.0.GA, 1.4.1.SP5
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
10:46 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-1165) Endless loop in PessimisticLockInterceptor
[ http://jira.jboss.com/jira/browse/JBCACHE-1165?page=comments#action_12376886 ]
Manik Surtani commented on JBCACHE-1165:
----------------------------------------
See org.jboss.cache.lock.pessimistic.ConcurrentPutRemoveTest which exhibits this problem
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: 2.0.0.GA, 1.4.1.SP4
Environment: Windows XP, Sun jdk150_06
Solaris 10
Reporter: Jacek Halat
Assigned To: Manik Surtani
Fix For: 2.1.0.GA, 1.4.1.SP5
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
1:43 p.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-1165) Endless loop in PessimisticLockInterceptor
[ http://jira.jboss.com/jira/browse/JBCACHE-1165?page=all ]
Manik Surtani updated JBCACHE-1165:
-----------------------------------
Fix Version/s: 1.4.1.SP6
(was: 1.4.1.SP5)
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: 2.0.0.GA, 1.4.1.SP4
Environment: Windows XP, Sun jdk150_06
Solaris 10
Reporter: Jacek Halat
Assigned To: Manik Surtani
Fix For: 2.1.0.GA, 1.4.1.SP6
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
9:51 a.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-1165) Endless loop in PessimisticLockInterceptor
[ http://jira.jboss.com/jira/browse/JBCACHE-1165?page=all ]
Manik Surtani updated JBCACHE-1165:
-----------------------------------
Fix Version/s: 1.4.1.SP7
(was: 1.4.1.SP6)
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: 2.0.0.GA, 1.4.1.SP4
Environment: Windows XP, Sun jdk150_06
Solaris 10
Reporter: Jacek Halat
Assigned To: Manik Surtani
Fix For: 2.1.0.GA, 1.4.1.SP7
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
10:33 a.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-1165) Endless loop in PessimisticLockInterceptor, sometimes seen as a NodeNotExistsException
[ http://jira.jboss.com/jira/browse/JBCACHE-1165?page=all ]
Manik Surtani updated JBCACHE-1165:
-----------------------------------
Summary: Endless loop in PessimisticLockInterceptor, sometimes seen as a
NodeNotExistsException (was: Endless loop in PessimisticLockInterceptor)
Description:
See ConcurrentPutRemoveTest
This sometimes manifests itself as an endless loop, and sometimes as a
NodeNotExistsException (on the putter thread) when concurrent puts and removes are
involved.
was:
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());
}
Endless loop in PessimisticLockInterceptor, sometimes seen as a
NodeNotExistsException
--------------------------------------------------------------------------------------
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: 2.0.0.GA, 1.4.1.SP4
Environment: Windows XP, Sun jdk150_06
Solaris 10
Reporter: Jacek Halat
Assigned To: Manik Surtani
Fix For: 2.1.0.GA, 1.4.1.SP7
Attachments: ConcurentPutRemoveTest.java, ConsoleOut.log
See ConcurrentPutRemoveTest
This sometimes manifests itself as an endless loop, and sometimes as a
NodeNotExistsException (on the putter thread) when concurrent puts and removes are
involved.
--
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
8:59 a.m.
New subject: [JBoss JIRA] Resolved: (JBCACHE-1165) Endless loop in PessimisticLockInterceptor, sometimes seen as a NodeNotExistsException
[ http://jira.jboss.com/jira/browse/JBCACHE-1165?page=all ]
Manik Surtani resolved JBCACHE-1165.
------------------------------------
Resolution: Done
This has been fixed.
The main parts of the fix (all in the pessimistic lock interceptor) involve:
1) Each time a lock is acquired (a call to acquireLock() from within the lock() method) we
re-check whether the node we got a lock on is the same node that is in memory (checking
object identity) since another thread may have deleted the node in question, and then yet
another thread may have recreated a new node object in it's place rendering the lock
just acquired invalid.
2) Make sure removeNode calls have createIfNotExists set to true. Since lock objects
exist on the node, acquiring a lock for a remove is meaningless if the node does not
exist.
Endless loop in PessimisticLockInterceptor, sometimes seen as a
NodeNotExistsException
--------------------------------------------------------------------------------------
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: 2.0.0.GA, 1.4.1.SP4
Environment: Windows XP, Sun jdk150_06
Solaris 10
Reporter: Jacek Halat
Assigned To: Manik Surtani
Fix For: 1.4.1.SP7, 2.1.0.GA
Attachments: ConcurentPutRemoveTest.java, ConsoleOut.log
See ConcurrentPutRemoveTest
This sometimes manifests itself as an endless loop, and sometimes as a
NodeNotExistsException (on the putter thread) when concurrent puts and removes are
involved.
--
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
7:42 a.m.
New subject: [JBoss JIRA] Reopened: (JBCACHE-1165) Endless loop in PessimisticLockInterceptor, sometimes seen as a NodeNotExistsException
[ http://jira.jboss.com/jira/browse/JBCACHE-1165?page=all ]
Manik Surtani reopened JBCACHE-1165:
------------------------------------
Endless loop in PessimisticLockInterceptor, sometimes seen as a
NodeNotExistsException
--------------------------------------------------------------------------------------
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: 2.0.0.GA, 1.4.1.SP4
Environment: Windows XP, Sun jdk150_06
Solaris 10
Reporter: Jacek Halat
Assigned To: Manik Surtani
Fix For: 2.1.0.GA, 1.4.1.SP7
Attachments: ConcurentPutRemoveTest.java, ConsoleOut.log
See ConcurrentPutRemoveTest
This sometimes manifests itself as an endless loop, and sometimes as a
NodeNotExistsException (on the putter thread) when concurrent puts and removes are
involved.
--
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
7:44 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-1165) Endless loop in PessimisticLockInterceptor, sometimes seen as a NodeNotExistsException
[ http://jira.jboss.com/jira/browse/JBCACHE-1165?page=comments#action_12387719 ]
Manik Surtani commented on JBCACHE-1165:
----------------------------------------
The fix is not absolute and will require pretty bug architectural changes.
There is an edge case where a NodeNotFoundException may occur, and this is due to parent
nodes not being
write locked when children are added/removed.
The problem is in the way READ_COMMITTED is implemented, i.e., writers are not blocked by
readers and this
allows a reader to hold a lock when a writer comes in and deletes the node in question.
Workaround is to use LockParentForChildInsertRemove OR to use REPEATABLE_READ.
Endless loop in PessimisticLockInterceptor, sometimes seen as a
NodeNotExistsException
--------------------------------------------------------------------------------------
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: 2.0.0.GA, 1.4.1.SP4
Environment: Windows XP, Sun jdk150_06
Solaris 10
Reporter: Jacek Halat
Assigned To: Manik Surtani
Fix For: 2.1.0.GA, 1.4.1.SP7
Attachments: ConcurentPutRemoveTest.java, ConsoleOut.log
See ConcurrentPutRemoveTest
This sometimes manifests itself as an endless loop, and sometimes as a
NodeNotExistsException (on the putter thread) when concurrent puts and removes are
involved.
--
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
7:46 a.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-1165) Endless loop in PessimisticLockInterceptor, sometimes seen as a NodeNotExistsException (when using READ_COMMITTED)
[ http://jira.jboss.com/jira/browse/JBCACHE-1165?page=all ]
Manik Surtani updated JBCACHE-1165:
-----------------------------------
Summary: Endless loop in PessimisticLockInterceptor, sometimes seen as
a NodeNotExistsException (when using READ_COMMITTED) (was: Endless loop in
PessimisticLockInterceptor, sometimes seen as a NodeNotExistsException)
Workaround Description: Use LockParentForChildInsertRemove OR REPEATABLE_READ
Environment:
Windows XP, Sun jdk150_06
Solaris 10
READ_COMMITTED
was:
Windows XP, Sun jdk150_06
Solaris 10
Workaround: [Workaround Exists]
Endless loop in PessimisticLockInterceptor, sometimes seen as a
NodeNotExistsException (when using READ_COMMITTED)
------------------------------------------------------------------------------------------------------------------
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: 2.0.0.GA, 1.4.1.SP4
Environment: Windows XP, Sun jdk150_06
Solaris 10
READ_COMMITTED
Reporter: Jacek Halat
Assigned To: Manik Surtani
Fix For: 2.1.0.GA, 1.4.1.SP7
Attachments: ConcurentPutRemoveTest.java, ConsoleOut.log
See ConcurrentPutRemoveTest
This sometimes manifests itself as an endless loop, and sometimes as a
NodeNotExistsException (on the putter thread) when concurrent puts and removes are
involved.
--
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
7:46 a.m.
New subject: [JBoss JIRA] Resolved: (JBCACHE-1165) Endless loop in PessimisticLockInterceptor, sometimes seen as a NodeNotExistsException (when using READ_COMMITTED)
[ http://jira.jboss.com/jira/browse/JBCACHE-1165?page=all ]
Manik Surtani resolved JBCACHE-1165.
------------------------------------
Resolution: Partially Completed
Endless loop in PessimisticLockInterceptor, sometimes seen as a
NodeNotExistsException (when using READ_COMMITTED)
------------------------------------------------------------------------------------------------------------------
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: 2.0.0.GA, 1.4.1.SP4
Environment: Windows XP, Sun jdk150_06
Solaris 10
READ_COMMITTED
Reporter: Jacek Halat
Assigned To: Manik Surtani
Fix For: 1.4.1.SP7, 2.1.0.GA
Attachments: ConcurentPutRemoveTest.java, ConsoleOut.log
See ConcurrentPutRemoveTest
This sometimes manifests itself as an endless loop, and sometimes as a
NodeNotExistsException (on the putter thread) when concurrent puts and removes are
involved.
--
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
4:36 a.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-1165) Endless loop in PessimisticLockInterceptor, sometimes seen as a NodeNotExistsException (when using READ_COMMITTED)
[ http://jira.jboss.com/jira/browse/JBCACHE-1165?page=all ]
Manik Surtani updated JBCACHE-1165:
-----------------------------------
Fix Version/s: 2.1.0.CR2
Endless loop in PessimisticLockInterceptor, sometimes seen as a
NodeNotExistsException (when using READ_COMMITTED)
------------------------------------------------------------------------------------------------------------------
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: 2.0.0.GA, 1.4.1.SP4
Environment: Windows XP, Sun jdk150_06
Solaris 10
READ_COMMITTED
Reporter: Jacek Halat
Assigned To: Manik Surtani
Fix For: 2.1.0.GA, 1.4.1.SP7, 2.1.0.CR2
Attachments: ConcurentPutRemoveTest.java, ConsoleOut.log
See ConcurrentPutRemoveTest
This sometimes manifests itself as an endless loop, and sometimes as a
NodeNotExistsException (on the putter thread) when concurrent puts and removes are
involved.
--
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
3:30 p.m.
New subject: [JBoss JIRA] Resolved: (JBCACHE-1165) Endless loop in PessimisticLockInterceptor, sometimes seen as a NodeNotExistsException (when using READ_COMMITTED)
[ http://jira.jboss.com/jira/browse/JBCACHE-1165?page=all ]
Brian Stansberry resolved JBCACHE-1165.
---------------------------------------
Fix Version/s: (was: 1.4.1.SP7)
Resolution: Partially Completed
Endless loop in PessimisticLockInterceptor, sometimes seen as a
NodeNotExistsException (when using READ_COMMITTED)
------------------------------------------------------------------------------------------------------------------
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: 2.0.0.GA, 1.4.1.SP4
Environment: Windows XP, Sun jdk150_06
Solaris 10
READ_COMMITTED
Reporter: Jacek Halat
Assigned To: Manik Surtani
Fix For: 2.1.0.GA, 2.1.0.CR2
Attachments: ConcurentPutRemoveTest.java, ConsoleOut.log
See ConcurrentPutRemoveTest
This sometimes manifests itself as an endless loop, and sometimes as a
NodeNotExistsException (on the putter thread) when concurrent puts and removes are
involved.
--
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
3:30 p.m.
New subject: [JBoss JIRA] Reopened: (JBCACHE-1165) Endless loop in PessimisticLockInterceptor, sometimes seen as a NodeNotExistsException (when using READ_COMMITTED)
[ http://jira.jboss.com/jira/browse/JBCACHE-1165?page=all ]
Brian Stansberry reopened JBCACHE-1165:
---------------------------------------
Reopening to remove the SP7 fix version as it is not fully fixed.
Endless loop in PessimisticLockInterceptor, sometimes seen as a
NodeNotExistsException (when using READ_COMMITTED)
------------------------------------------------------------------------------------------------------------------
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: 2.0.0.GA, 1.4.1.SP4
Environment: Windows XP, Sun jdk150_06
Solaris 10
READ_COMMITTED
Reporter: Jacek Halat
Assigned To: Manik Surtani
Fix For: 2.1.0.GA, 2.1.0.CR2
Attachments: ConcurentPutRemoveTest.java, ConsoleOut.log
See ConcurrentPutRemoveTest
This sometimes manifests itself as an endless loop, and sometimes as a
NodeNotExistsException (on the putter thread) when concurrent puts and removes are
involved.
--
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
5:52 p.m.
New subject: [JBoss JIRA] Reopened: (JBCACHE-1165) Endless loop in PessimisticLockInterceptor, sometimes seen as a NodeNotExistsException (when using READ_COMMITTED)
[ http://jira.jboss.com/jira/browse/JBCACHE-1165?page=all ]
Jason T. Greene reopened JBCACHE-1165:
--------------------------------------
The fix introduced another endless loop problem:
Line 441:
else
{
// do the loop again, but don't assign child_node to currentNode so that
child_node is processed again.
if (System.currentTimeMillis() > expiryTime)
{
throw new TimeoutException("Unable to acquire lock on child node
" + new Fqn(currentNode.getFqn(), childName) + " after " + timeout + "
millis.");
}
}
Since currentNode is not set to the peeked node, this code will loop until a timeout
occurs, at which point an exception is always thrown.
Endless loop in PessimisticLockInterceptor, sometimes seen as a
NodeNotExistsException (when using READ_COMMITTED)
------------------------------------------------------------------------------------------------------------------
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: 2.0.0.GA, 1.4.1.SP4
Environment: Windows XP, Sun jdk150_06
Solaris 10
READ_COMMITTED
Reporter: Jacek Halat
Assigned To: Manik Surtani
Fix For: 2.1.0.GA, 2.1.0.CR2
Attachments: ConcurentPutRemoveTest.java, ConsoleOut.log
See ConcurrentPutRemoveTest
This sometimes manifests itself as an endless loop, and sometimes as a
NodeNotExistsException (on the putter thread) when concurrent puts and removes are
involved.
--
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
5:54 p.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-1165) Endless loop in PessimisticLockInterceptor, sometimes seen as a NodeNotExistsException (when using READ_COMMITTED)
[ http://jira.jboss.com/jira/browse/JBCACHE-1165?page=all ]
Jason T. Greene updated JBCACHE-1165:
-------------------------------------
Fix Version/s: (was: 2.1.0.CR2)
Endless loop in PessimisticLockInterceptor, sometimes seen as a
NodeNotExistsException (when using READ_COMMITTED)
------------------------------------------------------------------------------------------------------------------
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: 2.0.0.GA, 1.4.1.SP4
Environment: Windows XP, Sun jdk150_06
Solaris 10
READ_COMMITTED
Reporter: Jacek Halat
Assigned To: Manik Surtani
Fix For: 2.1.0.GA
Attachments: ConcurentPutRemoveTest.java, ConsoleOut.log
See ConcurrentPutRemoveTest
This sometimes manifests itself as an endless loop, and sometimes as a
NodeNotExistsException (on the putter thread) when concurrent puts and removes are
involved.
--
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
3:34 a.m.
New subject: [JBoss JIRA] Assigned: (JBCACHE-1165) Endless loop in PessimisticLockInterceptor, sometimes seen as a NodeNotExistsException (when using READ_COMMITTED)
[ http://jira.jboss.com/jira/browse/JBCACHE-1165?page=all ]
Manik Surtani reassigned JBCACHE-1165:
--------------------------------------
Assignee: Mircea Markus (was: Manik Surtani)
Endless loop in PessimisticLockInterceptor, sometimes seen as a
NodeNotExistsException (when using READ_COMMITTED)
------------------------------------------------------------------------------------------------------------------
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: 2.0.0.GA, 1.4.1.SP4
Environment: Windows XP, Sun jdk150_06
Solaris 10
READ_COMMITTED
Reporter: Jacek Halat
Assigned To: Mircea Markus
Fix For: 2.1.0.GA
Attachments: ConcurentPutRemoveTest.java, ConsoleOut.log
See ConcurrentPutRemoveTest
This sometimes manifests itself as an endless loop, and sometimes as a
NodeNotExistsException (on the putter thread) when concurrent puts and removes are
involved.
--
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
9:44 a.m.
New subject: [JBoss JIRA] Resolved: (JBCACHE-1165) Endless loop in PessimisticLockInterceptor, sometimes seen as a NodeNotExistsException (when using READ_COMMITTED)
[ http://jira.jboss.com/jira/browse/JBCACHE-1165?page=all ]
Mircea Markus resolved JBCACHE-1165.
------------------------------------
Resolution: Done
the solution was to reenter the loop with current node being set to its parent.
Attached tests were successfully run.
Endless loop in PessimisticLockInterceptor, sometimes seen as a
NodeNotExistsException (when using READ_COMMITTED)
------------------------------------------------------------------------------------------------------------------
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: 2.0.0.GA, 1.4.1.SP4
Environment: Windows XP, Sun jdk150_06
Solaris 10
READ_COMMITTED
Reporter: Jacek Halat
Assigned To: Mircea Markus
Fix For: 2.1.0.GA
Attachments: ConcurentPutRemoveTest.java, ConsoleOut.log
See ConcurrentPutRemoveTest
This sometimes manifests itself as an endless loop, and sometimes as a
NodeNotExistsException (on the putter thread) when concurrent puts and removes are
involved.
--
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
6183
days inactive
6341
days old
19 comments
5 participants
participants (5)
-
Brian Stansberry (JIRA) -
Jacek Halat (JIRA)
-
Jason T. Greene (JIRA)
-
Manik Surtani (JIRA)
-
Mircea Markus (JIRA)