[hibernate-issues] [Hibernate-JIRA] Created: (HHH-4836) Infinispan: 2L QueryCache don't considers cached queries which belong to current transaction

[Guenther Demetz (JIRA)]

Infinispan: 2L QueryCache don't considers cached queries which belong to current transaction
--------------------------------------------------------------------------------------------

                 Key: HHH-4836
                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4836
             Project: Hibernate Core
          Issue Type: Bug
          Components: caching (L2)
    Affects Versions: 3.5.0-Beta-3, 3.5.0-Beta-2, 3.5.0.Beta-1
         Environment: 3.5.0.Beta3, SQLServerr2008, integration with JTA
            Reporter: Guenther Demetz


When looking for a cached Query in 2L-cache,
QueryResultsRegionImpl(BaseRegion) does temporary suspend the current transaction.
QueryResultsRegionImpl(BaseRegion).suspendAndGet(Object, FlagAdapter, boolean) line: 205	

In this way only committed queries from already closed transactions are considered to be hit.
Cached queries put by the current transaction are totally ignored!
This is in my opinion a bug, because it changes behavior and degrades the efficiency of the 2L QueryCache 
in respect to other 2L-implementations (for example EHCache).
Furthermore there is no reason to ignore cached queries deriving from current transaction:
the up-to-date-ness is checked anyway by the StandardQueryCache.isUpToDate() call.

Proposed solution:
simply not suspend current transaction when looking for cached querys,
then queries put by the current transaction are automatically considered as candidates for a hit.





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