[hibernate-issues] [Hibernate-JIRA] Reopened: (HHH-5793) Query and timestamp caches to use cluster cache loader to avoid behaving like sync repl caches
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5793?page=c...
]
Galder Zamarreno reopened HHH-5793:
-----------------------------------
Hmmm, something not totally right: see https://issues.jboss.org/browse/ISPN-832
Note to self: ClusterCacheLoader probably needs to have ignoreModifications set to true?
The point of the cache loader is to load data, but a cache loader cannot be written to, it
needs to be a cache store, and ClusterCacheLoader is not, so that probably is ignored.
Query and timestamp caches to use cluster cache loader to avoid
behaving like sync repl caches
----------------------------------------------------------------------------------------------
Key: HHH-5793
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5793
Project: Hibernate Core
Issue Type: Bug
Components: caching (L2)
Affects Versions: 3.5.6, 3.6.0
Reporter: Galder Zamarreno
Assignee: Galder Zamarreno
Fix For: 3.6.1, 4.0.0.Alpha1
As a result of the investigation carried out for
https://issues.jboss.org/browse/ISPN-832, it was found out that async caches that have
state transfer configured are effectively transformed into sync caches.
This is not desirable by any means, so while https://issues.jboss.org/browse/ISPN-835 is
addressed, Hibernate 2LC relying on this combo are switching to using a cluster cache
loader. This JIRA involves changing the default configuration and fixing some code to
maintain same semantics as before.
--
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira