[
https://issues.apache.org/jira/browse/SLING-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244077#comment-14244077
]
Vikas Saurabh commented on SLING-4216:
--------------------------------------
Sorry, I typed that in a hurry... I meant as far as I see the file isn't being
used to read the old state back (on start up). I was just trying to say that
once we implement that -- we'd need to take care of looking out for other
changes that might have happened in the repository while the instance was down
(and hence file doesn't have entries for vanity paths that might have got added
in the mean time).
> 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
> Attachments: 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)
