[Hibernate-issues] [Hibernate-JIRA] Closed: (HHH-1796) TreeCache based providers and Fqn

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

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

    Resolution: Fixed

The basic pattern discussed with Manik is:

Fqn regionFqn = Fqn.fromString( regionName.replace( '.', '/' ) );
cache.put( new Fqn( regionFqn, key ), ITEM, value, option );



> TreeCache based providers and Fqn
> ---------------------------------
>
>          Key: HHH-1796
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1796
>      Project: Hibernate3
>         Type: Improvement

>   Components: core
>     Reporter: Steve Ebersole
>     Assignee: Steve Ebersole
>      Fix For: 3.2.0

>
>
> Apparently we have not been using tree cache in the most proper manner in regards to Fqn construction.  The way in which we construct Fqns actually leads to a very flat tree structure.  For example consider a region for "org.hibernate.test.hql.Animal"; this actually leads to a tree node structured like:
> /org/hibernate/test/hql/Animal
>         /id1
>         /id2
>         /...
> Notice that the Hibernate region-name leads to a flat node which is a direct child of the root node...
> The issue is twofold:
> 1) This may be one of the causes of the high level of contention in the older pessimistic TreeCache model
> 2) This is currently causing problems with the optimistic locking stuff because the "parent" node is version-incremented whenever its children is mutated (child added/removed)

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