hibernate-issues

[Hibernate-issues] [Hibernate-JIRA] Created: (HHH-1911) evict has no effect with ReadWrite cache Strategy

[Michael K. (JIRA) <no...@at...>]

evict has no effect with ReadWrite cache Strategy
-------------------------------------------------

         Key: HHH-1911
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1911
     Project: Hibernate3
        Type: Bug

  Components: core  
    Versions: 3.1.3    
    Reporter: Michael Kopp


I first found this when my own Persister informed the EntityUpdateAction to invalidate the cache.

persister.isCacheInvalidationRequired()

The EntityUpdateAction dutifully calls evict on the Cache, but that did  not effect the cache state in any way. I looked into it and found that evict is a noop in ReadWrite Cache.
This breaks the consistence. The item is still in the cache after the update, unchange even after the transaction completed.
The next load will return a wrong state!!!

I digged a little more and found that the same thing happens on a delete too. the EntityDeleteAction calls evict but of course nothing happens.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Resolved: (HHH-1911) evict has no effect with ReadWrite cache Strategy

[Steve E. (JIRA) <no...@at...>]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1911?page=all ]
     
Steve Ebersole resolved HHH-1911:
---------------------------------

    Resolution: Fixed

No test case...

However, I seriously suggest you check out the following for the expetced call sequence:
http://fisheye.jboss.com/viewrep/Hibernate/trunk/Hibernate3/src/org/hibernate/cache/CacheConcurrencyStrategy.java?r=9247

> evict has no effect with ReadWrite cache Strategy
> -------------------------------------------------
>
>          Key: HHH-1911
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1911
>      Project: Hibernate3
>         Type: Bug

>   Components: core
>     Versions: 3.1.3
>     Reporter: Michael Kopp

>
>
> I first found this when my own Persister informed the EntityUpdateAction to invalidate the cache.
> persister.isCacheInvalidationRequired()
> The EntityUpdateAction dutifully calls evict on the Cache, but that did  not effect the cache state in any way. I looked into it and found that evict is a noop in ReadWrite Cache.
> This breaks the consistence. The item is still in the cache after the update, unchange even after the transaction completed.
> The next load will return a wrong state!!!
> I digged a little more and found that the same thing happens on a delete too. the EntityDeleteAction calls evict but of course nothing happens.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Resolved: (HHH-1911) evict has no effect with ReadWrite cache Strategy

[Steve E. (JIRA) <no...@at...>]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1911?page=all ]
     
Steve Ebersole resolved HHH-1911:
---------------------------------

    Resolution: Incomplete

> evict has no effect with ReadWrite cache Strategy
> -------------------------------------------------
>
>          Key: HHH-1911
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1911
>      Project: Hibernate3
>         Type: Bug

>   Components: core
>     Versions: 3.1.3
>     Reporter: Michael Kopp

>
>
> I first found this when my own Persister informed the EntityUpdateAction to invalidate the cache.
> persister.isCacheInvalidationRequired()
> The EntityUpdateAction dutifully calls evict on the Cache, but that did  not effect the cache state in any way. I looked into it and found that evict is a noop in ReadWrite Cache.
> This breaks the consistence. The item is still in the cache after the update, unchange even after the transaction completed.
> The next load will return a wrong state!!!
> I digged a little more and found that the same thing happens on a delete too. the EntityDeleteAction calls evict but of course nothing happens.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Reopened: (HHH-1911) evict has no effect with ReadWrite cache Strategy

[Steve E. (JIRA) <no...@at...>]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1911?page=all ]
     
Steve Ebersole reopened HHH-1911:
---------------------------------


> evict has no effect with ReadWrite cache Strategy
> -------------------------------------------------
>
>          Key: HHH-1911
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1911
>      Project: Hibernate3
>         Type: Bug

>   Components: core
>     Versions: 3.1.3
>     Reporter: Michael Kopp

>
>
> I first found this when my own Persister informed the EntityUpdateAction to invalidate the cache.
> persister.isCacheInvalidationRequired()
> The EntityUpdateAction dutifully calls evict on the Cache, but that did  not effect the cache state in any way. I looked into it and found that evict is a noop in ReadWrite Cache.
> This breaks the consistence. The item is still in the cache after the update, unchange even after the transaction completed.
> The next load will return a wrong state!!!
> I digged a little more and found that the same thing happens on a delete too. the EntityDeleteAction calls evict but of course nothing happens.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira