[hibernate-issues] [Hibernate-JIRA] Created: (HHH-2415) OptimisticTreeCache responsible for rety when DataVersioning exception occur

[Erwan Le Goulven (JIRA)]

OptimisticTreeCache responsible for rety when DataVersioning exception occur
----------------------------------------------------------------------------

         Key: HHH-2415
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2415
     Project: Hibernate3
        Type: New Feature

  Components: core  
    Versions: 3.2.2    
 Environment: 1.4.1SP1 Treecache use, on any of WAS 6.0X, Weblogic 9.x, JBOSS 4.x patched version
    Reporter: Erwan Le Goulven
    Priority: Critical


Messieurs, 
As mentioned in jboss cache doc
http://labs.jboss.com/file-access/default/members/jbosscache/freezone/docs/1.4.1/TreeCache/en/html_single/index.html#d0e567, Exception due to Dataversioning exception may occur when using jboss treecache as 2nd level cache in optimistic mode (which is, by the way, the recommended hibernate use).
>From an enterprise application user point of vue, I can't find normal for the persistency layer not to provide a way to handle version collision during concurrent access, letting the dev choose wether to retry/force commit against the cache, or to silently ignore such an exception.
Why do I consider the persistency layer to be responsible for that?
Well the main reason is that such an exception can occur at any time, during a Query Cache access, or during data loading from query result ...It occurs at a too deep level to be efficiently caught ant treated in a relevant manner.
Providing the OptimisticTreeCacheProvider class with the proper tooling would greatly enhance this near-perfect embracement class.

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