[
https://issues.apache.org/jira/browse/SLING-12435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert updated SLING-12435:
-----------------------------------
Description:
to be able to mitigate timeout issues or to evaluate if the actual timeout
value is really a problem, we should make the current timeout value
configurable. the current default value (adjusted in SLING-12415) is 500ms.
this timeout was introduced with SLING-12090, as newer resource resolver
implementation register resource resolver factories in an async way.
was:
to be able to mitigate timeout issues or to evaluate if the actual timeout
value is really a problem, we should make the current timeout value (250ms)
configurable, but keep the default value of 250ms.
this timeout was introduced with SLING-12090, as newer resource resolver
implementation register resource resolver factories in an async way.
as described in SLING-12415, we changed the default timeout value to 500ms -
updated ticket description accordingly.
> sling-mock: Make timeout to wait for ResourceResolverFactoryActivator
> configurable via system property
> ------------------------------------------------------------------------------------------------------
>
> Key: SLING-12435
> URL: https://issues.apache.org/jira/browse/SLING-12435
> Project: Sling
> Issue Type: Improvement
> Components: Testing
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Priority: Minor
> Fix For: Testing Sling Mock 3.5.4
>
>
> to be able to mitigate timeout issues or to evaluate if the actual timeout
> value is really a problem, we should make the current timeout value
> configurable. the current default value (adjusted in SLING-12415) is 500ms.
> this timeout was introduced with SLING-12090, as newer resource resolver
> implementation register resource resolver factories in an async way.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
