[hibernate-issues] [Hibernate-JIRA] Created: (HHH-3436) Second-level cache is not evicted on failure of update

[Fol De Rol (JIRA)]

Second-level cache is not evicted on failure of update
------------------------------------------------------

                 Key: HHH-3436
                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3436
             Project: Hibernate3
          Issue Type: Bug
    Affects Versions: 3.3.0.GA
            Reporter: Fol De Rol


Using cluster-wide TreeCache as a 2nd-level cache provider for Hibernate, I have noticed that in case of failure of update operation, e.g. in case of constraint violation, the object with inconsistent data is still persisted in the second-level cache. So, the forthcoming load() perfromed in a separate session/transaction returns the erroneous object from the cache instead of the actual state from the DB.

-- 
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