[jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1165) Endless loop in PessimisticLockInterceptor, sometimes seen as a NodeNotExistsException (when using READ_COMMITTED)

[Manik Surtani (JIRA)]

     [ 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