[hibernate-issues] [Hibernate-JIRA] Resolved: (HHH-4713) Avoid using same cache instance for storing CacheValue and evictAll notifications
Galder Zamarreno (JIRA)
noreply at atlassian.com
Thu Feb 2 03:53:10 EST 2012
[ https://hibernate.onjira.com/browse/HHH-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Galder Zamarreno resolved HHH-4713.
-----------------------------------
Resolution: Duplicate
This was fixed via HHH-6955
> Avoid using same cache instance for storing CacheValue and evictAll notifications
> ---------------------------------------------------------------------------------
>
> Key: HHH-4713
> URL: https://hibernate.onjira.com/browse/HHH-4713
> Project: Hibernate ORM
> Issue Type: Bug
> Components: caching (L2)
> Affects Versions: 3.5.0-Beta-2
> Reporter: Galder Zamarreno
> Assignee: Galder Zamarreno
>
> Store evictAll information in a separate infinispan cache instance in order to avoid doing stuff like this in BaseRegion.toMap which could be quite expensive in the context of SecondLevelCacheStatistics calculations:
> public Map toMap() {
> if (checkValid()) {
> // If copying causes issues, provide a lazily loaded Map
> Map map = new HashMap();
> Set<Map.Entry> entries = cacheAdapter.toMap().entrySet();
> for (Map.Entry entry : entries) {
> Object key = entry.getKey();
> if (!CacheHelper.isEvictAllNotification(key)) {
> map.put(key, entry.getValue());
> }
> }
> return map;
> }
> return Collections.EMPTY_MAP;
> }
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list