[
https://issues.apache.org/jira/browse/SLING-11363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17701065#comment-17701065
]
Wim Symons edited comment on SLING-11363 at 3/16/23 9:59 AM:
-------------------------------------------------------------
Affects 1.7.10 as well, it even rendered our AEM 6.5.15.0 unusable after a
restart (when bloom filter is read from disk), every path rendered a Resource
Not Found. Setting resource.resolver.vanitypath.maxEntries to -1 fixed it.
was (Author: wim.symons):
Affects 1.7.10 as well, it even rendered our AEM 6.5.15.0 dead, every path
rendered a Resource Not Found. Setting resource.resolver.vanitypath.maxEntries
to -1 fixed it.
> resource resolver: bloom filter incomplete when vanity path size limited
> ------------------------------------------------------------------------
>
> Key: SLING-11363
> URL: https://issues.apache.org/jira/browse/SLING-11363
> Project: Sling
> Issue Type: Bug
> Components: ResourceResolver
> Affects Versions: Resource Resolver 1.8.2
> Reporter: Julian Reschke
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: Resource Resolver 1.10.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> This was a problem before, but has easier to reproduce after SLING-11113:
> When reading the vanity paths, processing stops after the cache is full
> (where the default is 'unlimited'). In that case, additional paths are not
> added to the bloom filter, and thus the application of the bloom filter will
> cause them never to get looked up.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
