You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Philippe Mouawad (JIRA)" <ji...@apache.org> on 2011/03/19 12:38:29 UTC
[jira] Updated: (OFBIZ-4220) Current implementation of UtilCache
has a memory leak
[ https://issues.apache.org/jira/browse/OFBIZ-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Philippe Mouawad updated OFBIZ-4220:
------------------------------------
Attachment: patch_OFBIZ-4220.patch
Fix to the issue
Philippe
http://www.ubik-ingenierie.com
> Current implementation of UtilCache has a memory leak
> -----------------------------------------------------
>
> Key: OFBIZ-4220
> URL: https://issues.apache.org/jira/browse/OFBIZ-4220
> Project: OFBiz
> Issue Type: Bug
> Components: framework
> Affects Versions: SVN trunk
> Environment: ALL
> Reporter: Philippe Mouawad
> Labels: CACHE, LEAK, MEMORY
> Attachments: patch_OFBIZ-4220.patch
>
>
> Hello,
> Since some time UtilCache has been updated to replace the WeakHashMap by a ConcurrentHashMap:
> private static final ConcurrentHashMap<String, UtilCache<?, ?>> utilCacheTable = new ConcurrentHashMap<String, UtilCache<?, ?>>();
> I think this fix to concurrency issues has introduced a memory leak or at least a much bigger impact on Memory.
> Indeed descendent of AbstractCache (particularly AbstractEntityConditionCache, EntityListCache) tend to create many caches that do not need to always persist in time.
> The old WeakHashMap handled this by enabling them to disappear while today the Hard ref disables this.
> We made some load testing and current implementation ends with an OutOfMemory.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira