You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Georg Henzler (Jira)" <ji...@apache.org> on 2020/07/20 10:25:00 UTC
[jira] [Comment Edited] (SLING-9211) Startup detection not working
reliable anymore
[ https://issues.apache.org/jira/browse/SLING-9211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160960#comment-17160960 ]
Georg Henzler edited comment on SLING-9211 at 7/20/20, 10:24 AM:
-----------------------------------------------------------------
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 start level.
See also [^startup-ServiceUnavailableFilter-2nd-startup-works-fine.log] on how everything works fine (on second startup bundles start at start level 5 and configs become correctly active)
[~cziegeler] So I'm pretty sure the expected behaviour is currently broken... maybe you can have a look?
was (Author: henzlerg):
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-2nd-startup-works-fine.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)