[
https://issues.apache.org/jira/browse/SLING-9211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160960#comment-17160960
]
Georg Henzler commented on SLING-9211:
--------------------------------------
See attached [^startup-ServiceUnavailableFilter-too-late-registered.log] on
what is happening (the result of {{cat sling/logs/error.log | grep -E
"(ServiceUnavailable|health|Health)"}}). The only difference to the current
committed version is that I added a bundle with
org.apache.sling.starter.startup.impl.EventLogger that logs OSGi events
together with current startlevel.
[~cziegeler] So I'm pretty sure the expected behaviour is currently broken...
maybe you can have a look?
> 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-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)
