[jira] [Commented] (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=17160917#comment-17160917 ] Georg Henzler commented on SLING-9211: -- I analysed the problem and I think the problem only exists on first startup (subsequent startups seem fine). The following is happening: * the OSGi framework quickly "shoots up" to start level 30 * then the OSGi installer installs the bundles following the "conceptual start level order" as given by provisioning files but at actual start level 30 (also the start level is set to bundle for subsequent startups, but first startup installs everything on start level 30) * only once all bundles are installed the configurations are installed (there is a significant delay between installing a bundle and configurations that are meant for the bundle). * While the configurations for ServiceUnvailableFilter and systemready health checks are not available yet (delay from point above), the Sling startup page is not shown yet There are multiple options to fix the problem: # Extend health check core with a bundle activator that "forces the relevant configurations" into the systems ** I have tested this approach (using "felix.health.ServiceUnavailableFilter.*" framework properties) and it works, however it feels like a workaround # Change the launchpad to generally install configurations straight after the config admin is available (this seems conceptually the right thing to do for me, but there might be reasons for the current state that I'm not aware of) # Change the launchpad to mark certain configurations as "bootstrap" (or similar naming), only those are installed immediately after the config admin becomes available I also see that SLING-9498 introduced the possibility to run it with the feature model (maybe there configurations are respected as early as possible during startup? I haven't tried yet) [~cziegeler] WDYT, what option from above would be best? > 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 > > 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)
[RESULT][VOTE] Release Apache Sling Feature Model 1.2.4, Feature Model Analyser 1.3.2, Feature Model API Regions Extension 1.1.6, Feature Model API Regions Runtime Fragment 1.1.6, slingfeature-maven-p
With 4 binding +1 votes this release is successful. I've promoted the artifacts. Kind regards, David On Thu, 16 Jul 2020 at 17:03, wrote: > Hi all, > > I would like to call the release on the following Apache Sling components: > > Feature Model 1.2.4 > https://issues.apache.org/jira/projects/SLING/versions/12348403 > > Feature Model Analyser 1.3.2 > https://issues.apache.org/jira/projects/SLING/versions/12348404 > > Feature Model API Regions Extension 1.1.6 > https://issues.apache.org/jira/projects/SLING/versions/12347442 > > Feature Model API Regions Runtime Fragment 1.1.6 > https://issues.apache.org/jira/projects/SLING/versions/12348389 > > Content-Package to Feature Model Converter 1.0.12 > https://issues.apache.org/jira/projects/SLING/versions/12348542 > > slingfeature-maven-plugin 1.3.10 > https://issues.apache.org/jira/projects/SLING/versions/12348449 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2301 > > You can use this UNIX script to download the release and verify the > signatures: > > https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD > > Usage: > sh check_staged_release.sh 2301 /tmp/sling-staging > > Please vote to approve this release: > >[ ] +1 Approve the release >[ ] -1 Don't release, because ... > > This majority vote is open for at least 72 hours. > > Best regards, > > David >
Re: [VOTE] Release Apache Sling Feature Model 1.2.4, Feature Model Analyser 1.3.2, Feature Model API Regions Extension 1.1.6, Feature Model API Regions Runtime Fragment 1.1.6, slingfeature-maven-plugi
Here's my +1 David On Thu, 16 Jul 2020 at 17:03, wrote: > Hi all, > > I would like to call the release on the following Apache Sling components: > > Feature Model 1.2.4 > https://issues.apache.org/jira/projects/SLING/versions/12348403 > > Feature Model Analyser 1.3.2 > https://issues.apache.org/jira/projects/SLING/versions/12348404 > > Feature Model API Regions Extension 1.1.6 > https://issues.apache.org/jira/projects/SLING/versions/12347442 > > Feature Model API Regions Runtime Fragment 1.1.6 > https://issues.apache.org/jira/projects/SLING/versions/12348389 > > Content-Package to Feature Model Converter 1.0.12 > https://issues.apache.org/jira/projects/SLING/versions/12348542 > > slingfeature-maven-plugin 1.3.10 > https://issues.apache.org/jira/projects/SLING/versions/12348449 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2301 > > You can use this UNIX script to download the release and verify the > signatures: > > https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD > > Usage: > sh check_staged_release.sh 2301 /tmp/sling-staging > > Please vote to approve this release: > >[ ] +1 Approve the release >[ ] -1 Don't release, because ... > > This majority vote is open for at least 72 hours. > > Best regards, > > David >
