[hibernate-issues] [Hibernate-JIRA] Commented: (HV-479) Implement an eviction strategy for BeanMetaDataCache
Hardy Ferentschik (JIRA)
noreply at atlassian.com
Mon Dec 12 08:45:21 EST 2011
[ http://opensource.atlassian.com/projects/hibernate/browse/HV-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44559#comment-44559 ]
Hardy Ferentschik commented on HV-479:
--------------------------------------
Maybe if we switched to [ConcurrentWeakKeyHashMap|https://github.com/infinispan/infinispan/blob/master/core/src/main/java/org/infinispan/util/ConcurrentWeakKeyHashMap.java] as used by Infinispan and Netty!?
> Implement an eviction strategy for BeanMetaDataCache
> ----------------------------------------------------
>
> Key: HV-479
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-479
> Project: Hibernate Validator
> Issue Type: Improvement
> Components: engine
> Reporter: Gunnar Morling
> Fix For: 4.3.0.next
>
>
> In {{BeanMetaDataCache}} we have a map from {{Class}} to {{BeanMetaDataImpl}}. Currently there is no eviction strategy for this cache meaning entries will never be removed once they were added to the cache and the {{ValidatorFactoryImpl}} holding the cache exists.
> In particular this means that the concerned class objects never can be garbage-collected. This might cause problems in long-running applications (especially as there is typically one long-living {{ValidatorFactory}} instance per application). Maybe {{WeakHashMap}} or similar might be useful here.
--
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