You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2015/01/06 16:43:35 UTC
[jira] [Updated] (SLING-4216) Limit the number of vanityPath
MapEntry
[ https://issues.apache.org/jira/browse/SLING-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated SLING-4216:
------------------------------------
Fix Version/s: Resource Resolver 1.1.10
> Limit the number of vanityPath MapEntry
> ----------------------------------------
>
> Key: SLING-4216
> URL: https://issues.apache.org/jira/browse/SLING-4216
> Project: Sling
> Issue Type: Improvement
> Components: ResourceResolver
> Reporter: Antonio Sanso
> Assignee: Antonio Sanso
> Fix For: Resource Resolver 1.1.10
>
> Attachments: SLING-4216-patch.txt, SLING-4216-patch.txt, SLING-4216-patch.txt
>
>
> At the moment there isn't any limit to the number of MapEntry that are cached in memory.
> If the number of vanityPaths/alias is extremely high this can cause OOM.
> It would be good to have a way to limit the amount of memory used by the MapEntry cache.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)