]
Strong Liu resolved HHH-4055.
-----------------------------
Resolution: Fixed
Fix Version/s: 4.0.0.next
I believe this is possible now in hibernate 4.0 by the new introduced ServiceRegistry
since RegionFactory is now a Service, you can build your own service impl and return your
own UpdateTimestampCache impl
make UpdateTimestampsCache pluggable, like QueryCache
-----------------------------------------------------
Key: HHH-4055
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4055
Project: Hibernate Core
Issue Type: Improvement
Components: caching (L2)
Affects Versions: 3.3.2
Environment: all
Reporter: A. R.
Fix For: 4.0.0.next
According to
https://www.hibernate.org/213.html, one can plug-in one's own query
cache using hibernate.cache.query_cache_factory, e.g. to chose a cache strategy that is
not based on updateTimestamps.
However, Hibernate's SessionFactoryImpl will always create an UpdateTimestampsCache
if the Query Cache is enabled, even for custom Query Caches. This UpdateTimestampsCache
then is always used in org.hibernate.engine.ActionQueue.execute() and
afterTransactionCompletion(). Since the UpdateTimestampsCache is synchronized, this can
cause bottlenecks when many threads change things (see
http://tech.puredanger.com/2009/07/10/hibernate-query-cache/)..
Please make the UpdateTimestampsCache also pluggable, so that one can truly and
completely plug one's own Query Cache without using a Update-Timestamps or with a
custom UpdateTimestampCache.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: