[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=17161126#comment-17161126 ] Robert Munteanu edited comment on SLING-9211 at 7/20/20, 10:33 AM: --- [~ghenzler] - the current plan is to ship Starter 12 based on the feature model. We are done with Phase 1 as defined in https://cwiki.apache.org/confluence/display/SLING/Migrating+the+Sling+Starter+to+the+Feature+Model and I will start creating Jira issues for Phase 2 this week. was (Author: rombert): [~ghenzler] - the current plan is to ship Starter 12 based on the feature model. We are done with Phase 1 as defined in https://cwiki.apache.org/confluence/display/SLING/Migrating+the+Sling+Starter+to+the+Feature+Model and I will start defining tasks for Phase 2 this week. > 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=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16813130 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[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=17161122#comment-17161122 ] Georg Henzler edited comment on SLING-9211 at 7/20/20, 10:28 AM: - [~rombert] I think at the moment the feature model variant is marked as experimental in README.md - but if we swap over soon we obviously don't need to fix "the old world" (I think the problem described is more in project org.apache.sling.launchpad.installer than in OSGi installer, but also that will be deprecated soon I suppose). I'm testing now the experimental feature model variant was (Author: henzlerg): [~rombert] I think at the moment the feature model variant is marked as experimental README.md - but if we swap over soon we obviously don't need to fix "the old world" (I think the problem described is more in project org.apache.sling.launchpad.installer than in OSGi installer, but also that will be deprecated soon I suppose). I'm testing now the experimental feature model variant > 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=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16813130 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[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=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=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16813130
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
