[
https://issues.apache.org/jira/browse/SLING-12250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17868334#comment-17868334
]
Henry Kuijpers commented on SLING-12250:
----------------------------------------
A fix for this was to ignore the exception.
```
await()
.ignoreException(RejectedExecutionException.class)
.atMost(10, TimeUnit.MINUTES)
.ignoreException(RejectedExecutionException.class)
.until(() -> context.resourceResolver().resolve("/test"),
path("/content/mypath"));
```
> Adding Resource with sling:vanityPath set causes mismatch when resolving
> vanity URL (timing issue)
> --------------------------------------------------------------------------------------------------
>
> Key: SLING-12250
> URL: https://issues.apache.org/jira/browse/SLING-12250
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Affects Versions: Testing Sling Mock 3.4.18
> Reporter: Henry Kuijpers
> Priority: Major
>
> It could happen that a Resource containing sling:vanityPath is added and then
> resolved, but the Resource did not end up yet in the vanity logic.
> Observed with JCR_OAK mock context.
> Adding Thread.sleep(1000) fixes the issue, but it's of course not a very good
> solution.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
