[
https://issues.apache.org/jira/browse/SLING-9211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161186#comment-17161186
]
Georg Henzler commented on SLING-9211:
--------------------------------------
So I checked with
{code}
java -jar org.apache.sling.feature.launcher-1.1.4.jar -f
target/slingfeature-tmp/feature-oak_tar.json
{code}
that produced the log file
[^startup-ServiceUnavailableFilter-first-startup-feature-launcher.log]. It
works well and the ServiceUnavailableFilter is correctly activated at start
level 5 on first start already.
> Startup detection not working reliable anymore
> ----------------------------------------------
>
> Key: SLING-9211
> URL: https://issues.apache.org/jira/browse/SLING-9211
> Project: Sling
> Issue Type: Improvement
> Components: Starter
> Reporter: Georg Henzler
> Assignee: Georg Henzler
> Priority: Major
> Attachments:
> startup-ServiceUnavailableFilter-2nd-startup-works-fine.log,
> startup-ServiceUnavailableFilter-first-startup-feature-launcher.log,
> startup-ServiceUnavailableFilter-too-late-registered.log
>
>
> It seems with SLING-8418 the 503 responses are not as reliable as with the
> previous custom solution.
> To be checked with script in
> https://issues.apache.org/jira/browse/FELIX-6097?focusedCommentId=16813130&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16813130
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
