You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@karaf.apache.org by Stefan Günst <st...@me.com> on 2021/08/18 15:19:16 UTC
Significance of featuresBootAsynchronous - can you explain?
Hello,
can anyone explain what this is for/what it does and why it is default = false.
We have situations where it helps to start our distribution without any errors if we set this to „true“ in org.apache.karaf.features.cfg
Any risk to set it to true?
Stefan
Re: Significance of featuresBootAsynchronous - can you explain?
Posted by Stefan Günst <st...@me.com>.
Hi,
can’t nobody give us a hint?
Regards
Stefan
> Am 31.08.2021 um 16:00 schrieb Stefan Günst <st...@me.com>:
>
> Hi,
>
> no one can comment ?
>
>
>> Am 18.08.2021 um 17:19 schrieb Stefan Günst <st...@me.com>:
>>
>> Hello,
>>
>> can anyone explain what this is for/what it does and why it is default = false.
>> We have situations where it helps to start our distribution without any errors if we set this to „true“ in org.apache.karaf.features.cfg
>>
>> Any risk to set it to true?
>>
>>
>>
>> Stefan
>>
>>
>>
>>
>
Re: Significance of featuresBootAsynchronous - can you explain?
Posted by Jean-Baptiste Onofre <jb...@nanthrax.net>.
Hi guys,
The karaf-maven-plugin can take a features.xml as « template » where only the actual version will be populated with your pom dependencies set.
Generally speaking, it’s the same as using the maven interpolation (it’s this approach we are using in Karaf itself).
IMHO, you have more control and it’s easier to use maven interpolation with your features XML:
https://github.com/apache/karaf/tree/main/assemblies/features/standard
Regards
JB
> Le 19 sept. 2021 à 10:16, Steven Huypens <st...@gmail.com> a écrit :
>
> Hi JB,
>
> Still interested ;-)
>
> Kind regards,
> Steven
>
> On Tue, Sep 14, 2021 at 8:32 AM Stefan Günst <st...@me.com> wrote:
> Hi JB,
>
> we would also be very interested on this
>
> Regards
> Stefan
>
>
>> Am 13.09.2021 um 21:30 schrieb Steven Huypens <st...@gmail.com>:
>>
>> Hi JB,
>>
>> Thanks for your answer! I'm sorry I have to ask, but can you also explain what you mean by a 'template file' ?
>>
>> Kind regards,
>> Steven
>>
>> On Mon, Sep 13, 2021 at 8:51 PM Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>> Hi,
>>
>> It's not possible directly in the maven plugin (see
>> https://issues.apache.org/jira/browse/KARAF-7246), the workaround is to
>> use a template file.
>>
>> Regards
>> JB
>>
>> On 13/09/2021 19:03, Steven Huypens wrote:
>> > Hi JB,
>> >
>> > I could not find how to implement such a 'stage' using the
>> > <bootFeatures> from the karaf-maven-plugin. Do you know where I can find
>> > an example ?
>> >
>> > Kind regards,
>> > Steven
>> >
>> > On Mon, Sep 13, 2021 at 6:22 PM Jean-Baptiste Onofre <jb@nanthrax.net
>> > <ma...@nanthrax.net>> wrote:
>> >
>> > Exactly, you are in the case where stage can help ;)
>> >
>> > Regards
>> > JB
>> >
>> > > Le 13 sept. 2021 à 18:06, Stefan Günst <stefan.guenst@me.com
>> > <ma...@me.com>> a écrit :
>> > >
>> > > Hi JB,
>> > >
>> > > so the strict order of features guarantees that (in sync mode the
>> > default).
>> > > That is how we do it at the moment.
>> > >
>> > > But: we got situation sometimes on slow systems clean start where
>> > we start feature „war“ and than later the webapp that needed this
>> > but got error unknown protocol „war“ …
>> > >
>> > > Regards
>> > >
>> > > Stefan
>> > >
>> > >
>> > >
>> > >
>> > >> Am 13.09.2021 um 17:50 schrieb Jean-Baptiste Onofré
>> > <jb@nanthrax.net <ma...@nanthrax.net>>:
>> > >>
>> > >> Hi Stefan,
>> > >>
>> > >> I guess you mean stage in boot features.
>> > >>
>> > >> The use case is when you have boot features that requires
>> > another boot features to start or a specific order.
>> > >>
>> > >> The stage allows you to "force" the installation of some
>> > features before others.
>> > >>
>> > >> featuresBoot=(A,B),C,D
>> > >>
>> > >> We are "sure" that A and B are completely installed before
>> > installing C and D features.
>> > >>
>> > >> Classic example is wrap: if you need wrap in your feature, you
>> > have to install wrap before your feature, so you put wrap in the
>> > first stage.
>> > >>
>> > >> Regards
>> > >> JB
>> > >>
>> > >> On 13/09/2021 17:24, Stefan Günst wrote:
>> > >>> Hi JB,
>> > >>> thank you very much!
>> > >>>
>> > >>>> The same applies with stage:
>> > >>> That is very interesting and i think we dont know the possibility!
>> > >>> Can you give us a hint/link how to control this in a real scenario?
>> > >>> Regards
>> > >>> Stefan
>> > >>>> Am 13.09.2021 um 14:07 schrieb Jean-Baptiste Onofré
>> > <jb@nanthrax.net <ma...@nanthrax.net>>:
>> > >>>>
>> > >>>> Hi Stefan,
>> > >>>>
>> > >>>> sorry, I missed your message.
>> > >>>>
>> > >>>> By default, the boot features are started in sequence (sync)
>> > meaning:
>> > >>>>
>> > >>>> featuresBoot=A,B,C
>> > >>>>
>> > >>>> means first A will be installed, and then, once A is
>> > completely installed, B will be installed, etc
>> > >>>>
>> > >>>> The same applies with stage:
>> > >>>>
>> > >>>> featuresBoot=(A,C),B
>> > >>>>
>> > >>>> so, A will be installed then C, then once A and C are fully
>> > installed, B will be installed.
>> > >>>>
>> > >>>> In async mode, A,B,C will be installed in parallel and the
>> > resolver will try to find the optimal order.
>> > >>>> The purpose is to speed up the startup but it's "less"
>> > predictable.
>> > >>>>
>> > >>>> Regards
>> > >>>> JB
>> > >>>>
>> > >>>> On 31/08/2021 16:00, Stefan Günst wrote:
>> > >>>>> Hi,
>> > >>>>> no one can comment ?
>> > >>>>>> Am 18.08.2021 um 17:19 schrieb Stefan Günst
>> > <stefan.guenst@me.com <ma...@me.com>>:
>> > >>>>>>
>> > >>>>>> Hello,
>> > >>>>>>
>> > >>>>>> can anyone explain what this is for/what it does and why it
>> > is default = false.
>> > >>>>>> We have situations where it helps to start our distribution
>> > without any errors if we set this to „true“ in
>> > org.apache.karaf.features.cfg
>> > >>>>>>
>> > >>>>>> Any risk to set it to true?
>> > >>>>>>
>> > >>>>>>
>> > >>>>>>
>> > >>>>>> Stefan
>> > >>>>>>
>> > >>>>>>
>> > >>>>>>
>> > >>>>>>
>> > >
>> >
>
Re: Significance of featuresBootAsynchronous - can you explain?
Posted by Steven Huypens <st...@gmail.com>.
Hi JB,
Still interested ;-)
Kind regards,
Steven
On Tue, Sep 14, 2021 at 8:32 AM Stefan Günst <st...@me.com> wrote:
> Hi JB,
>
> we would also be very interested on this
>
> Regards
> Stefan
>
>
> Am 13.09.2021 um 21:30 schrieb Steven Huypens <st...@gmail.com>:
>
> Hi JB,
>
> Thanks for your answer! I'm sorry I have to ask, but can you also explain
> what you mean by a 'template file' ?
>
> Kind regards,
> Steven
>
> On Mon, Sep 13, 2021 at 8:51 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
>> Hi,
>>
>> It's not possible directly in the maven plugin (see
>> https://issues.apache.org/jira/browse/KARAF-7246), the workaround is to
>> use a template file.
>>
>> Regards
>> JB
>>
>> On 13/09/2021 19:03, Steven Huypens wrote:
>> > Hi JB,
>> >
>> > I could not find how to implement such a 'stage' using the
>> > <bootFeatures> from the karaf-maven-plugin. Do you know where I can
>> find
>> > an example ?
>> >
>> > Kind regards,
>> > Steven
>> >
>> > On Mon, Sep 13, 2021 at 6:22 PM Jean-Baptiste Onofre <jb@nanthrax.net
>> > <ma...@nanthrax.net>> wrote:
>> >
>> > Exactly, you are in the case where stage can help ;)
>> >
>> > Regards
>> > JB
>> >
>> > > Le 13 sept. 2021 à 18:06, Stefan Günst <stefan.guenst@me.com
>> > <ma...@me.com>> a écrit :
>> > >
>> > > Hi JB,
>> > >
>> > > so the strict order of features guarantees that (in sync mode the
>> > default).
>> > > That is how we do it at the moment.
>> > >
>> > > But: we got situation sometimes on slow systems clean start where
>> > we start feature „war“ and than later the webapp that needed this
>> > but got error unknown protocol „war“ …
>> > >
>> > > Regards
>> > >
>> > > Stefan
>> > >
>> > >
>> > >
>> > >
>> > >> Am 13.09.2021 um 17:50 schrieb Jean-Baptiste Onofré
>> > <jb@nanthrax.net <ma...@nanthrax.net>>:
>> > >>
>> > >> Hi Stefan,
>> > >>
>> > >> I guess you mean stage in boot features.
>> > >>
>> > >> The use case is when you have boot features that requires
>> > another boot features to start or a specific order.
>> > >>
>> > >> The stage allows you to "force" the installation of some
>> > features before others.
>> > >>
>> > >> featuresBoot=(A,B),C,D
>> > >>
>> > >> We are "sure" that A and B are completely installed before
>> > installing C and D features.
>> > >>
>> > >> Classic example is wrap: if you need wrap in your feature, you
>> > have to install wrap before your feature, so you put wrap in the
>> > first stage.
>> > >>
>> > >> Regards
>> > >> JB
>> > >>
>> > >> On 13/09/2021 17:24, Stefan Günst wrote:
>> > >>> Hi JB,
>> > >>> thank you very much!
>> > >>>
>> > >>>> The same applies with stage:
>> > >>> That is very interesting and i think we dont know the
>> possibility!
>> > >>> Can you give us a hint/link how to control this in a real
>> scenario?
>> > >>> Regards
>> > >>> Stefan
>> > >>>> Am 13.09.2021 um 14:07 schrieb Jean-Baptiste Onofré
>> > <jb@nanthrax.net <ma...@nanthrax.net>>:
>> > >>>>
>> > >>>> Hi Stefan,
>> > >>>>
>> > >>>> sorry, I missed your message.
>> > >>>>
>> > >>>> By default, the boot features are started in sequence (sync)
>> > meaning:
>> > >>>>
>> > >>>> featuresBoot=A,B,C
>> > >>>>
>> > >>>> means first A will be installed, and then, once A is
>> > completely installed, B will be installed, etc
>> > >>>>
>> > >>>> The same applies with stage:
>> > >>>>
>> > >>>> featuresBoot=(A,C),B
>> > >>>>
>> > >>>> so, A will be installed then C, then once A and C are fully
>> > installed, B will be installed.
>> > >>>>
>> > >>>> In async mode, A,B,C will be installed in parallel and the
>> > resolver will try to find the optimal order.
>> > >>>> The purpose is to speed up the startup but it's "less"
>> > predictable.
>> > >>>>
>> > >>>> Regards
>> > >>>> JB
>> > >>>>
>> > >>>> On 31/08/2021 16:00, Stefan Günst wrote:
>> > >>>>> Hi,
>> > >>>>> no one can comment ?
>> > >>>>>> Am 18.08.2021 um 17:19 schrieb Stefan Günst
>> > <stefan.guenst@me.com <ma...@me.com>>:
>> > >>>>>>
>> > >>>>>> Hello,
>> > >>>>>>
>> > >>>>>> can anyone explain what this is for/what it does and why it
>> > is default = false.
>> > >>>>>> We have situations where it helps to start our distribution
>> > without any errors if we set this to „true“ in
>> > org.apache.karaf.features.cfg
>> > >>>>>>
>> > >>>>>> Any risk to set it to true?
>> > >>>>>>
>> > >>>>>>
>> > >>>>>>
>> > >>>>>> Stefan
>> > >>>>>>
>> > >>>>>>
>> > >>>>>>
>> > >>>>>>
>> > >
>> >
>>
>
>
Re: Significance of featuresBootAsynchronous - can you explain?
Posted by Stefan Günst <st...@me.com>.
Hi JB,
we would also be very interested on this
Regards
Stefan
> Am 13.09.2021 um 21:30 schrieb Steven Huypens <st...@gmail.com>:
>
> Hi JB,
>
> Thanks for your answer! I'm sorry I have to ask, but can you also explain what you mean by a 'template file' ?
>
> Kind regards,
> Steven
>
> On Mon, Sep 13, 2021 at 8:51 PM Jean-Baptiste Onofré <jb@nanthrax.net <ma...@nanthrax.net>> wrote:
> Hi,
>
> It's not possible directly in the maven plugin (see
> https://issues.apache.org/jira/browse/KARAF-7246 <https://issues.apache.org/jira/browse/KARAF-7246>), the workaround is to
> use a template file.
>
> Regards
> JB
>
> On 13/09/2021 19:03, Steven Huypens wrote:
> > Hi JB,
> >
> > I could not find how to implement such a 'stage' using the
> > <bootFeatures> from the karaf-maven-plugin. Do you know where I can find
> > an example ?
> >
> > Kind regards,
> > Steven
> >
> > On Mon, Sep 13, 2021 at 6:22 PM Jean-Baptiste Onofre <jb@nanthrax.net <ma...@nanthrax.net>
> > <mailto:jb@nanthrax.net <ma...@nanthrax.net>>> wrote:
> >
> > Exactly, you are in the case where stage can help ;)
> >
> > Regards
> > JB
> >
> > > Le 13 sept. 2021 à 18:06, Stefan Günst <stefan.guenst@me.com <ma...@me.com>
> > <mailto:stefan.guenst@me.com <ma...@me.com>>> a écrit :
> > >
> > > Hi JB,
> > >
> > > so the strict order of features guarantees that (in sync mode the
> > default).
> > > That is how we do it at the moment.
> > >
> > > But: we got situation sometimes on slow systems clean start where
> > we start feature „war“ and than later the webapp that needed this
> > but got error unknown protocol „war“ …
> > >
> > > Regards
> > >
> > > Stefan
> > >
> > >
> > >
> > >
> > >> Am 13.09.2021 um 17:50 schrieb Jean-Baptiste Onofré
> > <jb@nanthrax.net <ma...@nanthrax.net> <mailto:jb@nanthrax.net <ma...@nanthrax.net>>>:
> > >>
> > >> Hi Stefan,
> > >>
> > >> I guess you mean stage in boot features.
> > >>
> > >> The use case is when you have boot features that requires
> > another boot features to start or a specific order.
> > >>
> > >> The stage allows you to "force" the installation of some
> > features before others.
> > >>
> > >> featuresBoot=(A,B),C,D
> > >>
> > >> We are "sure" that A and B are completely installed before
> > installing C and D features.
> > >>
> > >> Classic example is wrap: if you need wrap in your feature, you
> > have to install wrap before your feature, so you put wrap in the
> > first stage.
> > >>
> > >> Regards
> > >> JB
> > >>
> > >> On 13/09/2021 17:24, Stefan Günst wrote:
> > >>> Hi JB,
> > >>> thank you very much!
> > >>>
> > >>>> The same applies with stage:
> > >>> That is very interesting and i think we dont know the possibility!
> > >>> Can you give us a hint/link how to control this in a real scenario?
> > >>> Regards
> > >>> Stefan
> > >>>> Am 13.09.2021 um 14:07 schrieb Jean-Baptiste Onofré
> > <jb@nanthrax.net <ma...@nanthrax.net> <mailto:jb@nanthrax.net <ma...@nanthrax.net>>>:
> > >>>>
> > >>>> Hi Stefan,
> > >>>>
> > >>>> sorry, I missed your message.
> > >>>>
> > >>>> By default, the boot features are started in sequence (sync)
> > meaning:
> > >>>>
> > >>>> featuresBoot=A,B,C
> > >>>>
> > >>>> means first A will be installed, and then, once A is
> > completely installed, B will be installed, etc
> > >>>>
> > >>>> The same applies with stage:
> > >>>>
> > >>>> featuresBoot=(A,C),B
> > >>>>
> > >>>> so, A will be installed then C, then once A and C are fully
> > installed, B will be installed.
> > >>>>
> > >>>> In async mode, A,B,C will be installed in parallel and the
> > resolver will try to find the optimal order.
> > >>>> The purpose is to speed up the startup but it's "less"
> > predictable.
> > >>>>
> > >>>> Regards
> > >>>> JB
> > >>>>
> > >>>> On 31/08/2021 16:00, Stefan Günst wrote:
> > >>>>> Hi,
> > >>>>> no one can comment ?
> > >>>>>> Am 18.08.2021 um 17:19 schrieb Stefan Günst
> > <stefan.guenst@me.com <ma...@me.com> <mailto:stefan.guenst@me.com <ma...@me.com>>>:
> > >>>>>>
> > >>>>>> Hello,
> > >>>>>>
> > >>>>>> can anyone explain what this is for/what it does and why it
> > is default = false.
> > >>>>>> We have situations where it helps to start our distribution
> > without any errors if we set this to „true“ in
> > org.apache.karaf.features.cfg
> > >>>>>>
> > >>>>>> Any risk to set it to true?
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> Stefan
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >
> >
Re: Significance of featuresBootAsynchronous - can you explain?
Posted by Steven Huypens <st...@gmail.com>.
Hi JB,
Thanks for your answer! I'm sorry I have to ask, but can you also explain
what you mean by a 'template file' ?
Kind regards,
Steven
On Mon, Sep 13, 2021 at 8:51 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> Hi,
>
> It's not possible directly in the maven plugin (see
> https://issues.apache.org/jira/browse/KARAF-7246), the workaround is to
> use a template file.
>
> Regards
> JB
>
> On 13/09/2021 19:03, Steven Huypens wrote:
> > Hi JB,
> >
> > I could not find how to implement such a 'stage' using the
> > <bootFeatures> from the karaf-maven-plugin. Do you know where I can find
> > an example ?
> >
> > Kind regards,
> > Steven
> >
> > On Mon, Sep 13, 2021 at 6:22 PM Jean-Baptiste Onofre <jb@nanthrax.net
> > <ma...@nanthrax.net>> wrote:
> >
> > Exactly, you are in the case where stage can help ;)
> >
> > Regards
> > JB
> >
> > > Le 13 sept. 2021 à 18:06, Stefan Günst <stefan.guenst@me.com
> > <ma...@me.com>> a écrit :
> > >
> > > Hi JB,
> > >
> > > so the strict order of features guarantees that (in sync mode the
> > default).
> > > That is how we do it at the moment.
> > >
> > > But: we got situation sometimes on slow systems clean start where
> > we start feature „war“ and than later the webapp that needed this
> > but got error unknown protocol „war“ …
> > >
> > > Regards
> > >
> > > Stefan
> > >
> > >
> > >
> > >
> > >> Am 13.09.2021 um 17:50 schrieb Jean-Baptiste Onofré
> > <jb@nanthrax.net <ma...@nanthrax.net>>:
> > >>
> > >> Hi Stefan,
> > >>
> > >> I guess you mean stage in boot features.
> > >>
> > >> The use case is when you have boot features that requires
> > another boot features to start or a specific order.
> > >>
> > >> The stage allows you to "force" the installation of some
> > features before others.
> > >>
> > >> featuresBoot=(A,B),C,D
> > >>
> > >> We are "sure" that A and B are completely installed before
> > installing C and D features.
> > >>
> > >> Classic example is wrap: if you need wrap in your feature, you
> > have to install wrap before your feature, so you put wrap in the
> > first stage.
> > >>
> > >> Regards
> > >> JB
> > >>
> > >> On 13/09/2021 17:24, Stefan Günst wrote:
> > >>> Hi JB,
> > >>> thank you very much!
> > >>>
> > >>>> The same applies with stage:
> > >>> That is very interesting and i think we dont know the
> possibility!
> > >>> Can you give us a hint/link how to control this in a real
> scenario?
> > >>> Regards
> > >>> Stefan
> > >>>> Am 13.09.2021 um 14:07 schrieb Jean-Baptiste Onofré
> > <jb@nanthrax.net <ma...@nanthrax.net>>:
> > >>>>
> > >>>> Hi Stefan,
> > >>>>
> > >>>> sorry, I missed your message.
> > >>>>
> > >>>> By default, the boot features are started in sequence (sync)
> > meaning:
> > >>>>
> > >>>> featuresBoot=A,B,C
> > >>>>
> > >>>> means first A will be installed, and then, once A is
> > completely installed, B will be installed, etc
> > >>>>
> > >>>> The same applies with stage:
> > >>>>
> > >>>> featuresBoot=(A,C),B
> > >>>>
> > >>>> so, A will be installed then C, then once A and C are fully
> > installed, B will be installed.
> > >>>>
> > >>>> In async mode, A,B,C will be installed in parallel and the
> > resolver will try to find the optimal order.
> > >>>> The purpose is to speed up the startup but it's "less"
> > predictable.
> > >>>>
> > >>>> Regards
> > >>>> JB
> > >>>>
> > >>>> On 31/08/2021 16:00, Stefan Günst wrote:
> > >>>>> Hi,
> > >>>>> no one can comment ?
> > >>>>>> Am 18.08.2021 um 17:19 schrieb Stefan Günst
> > <stefan.guenst@me.com <ma...@me.com>>:
> > >>>>>>
> > >>>>>> Hello,
> > >>>>>>
> > >>>>>> can anyone explain what this is for/what it does and why it
> > is default = false.
> > >>>>>> We have situations where it helps to start our distribution
> > without any errors if we set this to „true“ in
> > org.apache.karaf.features.cfg
> > >>>>>>
> > >>>>>> Any risk to set it to true?
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> Stefan
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >
> >
>
Re: Significance of featuresBootAsynchronous - can you explain?
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi,
It's not possible directly in the maven plugin (see
https://issues.apache.org/jira/browse/KARAF-7246), the workaround is to
use a template file.
Regards
JB
On 13/09/2021 19:03, Steven Huypens wrote:
> Hi JB,
>
> I could not find how to implement such a 'stage' using the
> <bootFeatures> from the karaf-maven-plugin. Do you know where I can find
> an example ?
>
> Kind regards,
> Steven
>
> On Mon, Sep 13, 2021 at 6:22 PM Jean-Baptiste Onofre <jb@nanthrax.net
> <ma...@nanthrax.net>> wrote:
>
> Exactly, you are in the case where stage can help ;)
>
> Regards
> JB
>
> > Le 13 sept. 2021 à 18:06, Stefan Günst <stefan.guenst@me.com
> <ma...@me.com>> a écrit :
> >
> > Hi JB,
> >
> > so the strict order of features guarantees that (in sync mode the
> default).
> > That is how we do it at the moment.
> >
> > But: we got situation sometimes on slow systems clean start where
> we start feature „war“ and than later the webapp that needed this
> but got error unknown protocol „war“ …
> >
> > Regards
> >
> > Stefan
> >
> >
> >
> >
> >> Am 13.09.2021 um 17:50 schrieb Jean-Baptiste Onofré
> <jb@nanthrax.net <ma...@nanthrax.net>>:
> >>
> >> Hi Stefan,
> >>
> >> I guess you mean stage in boot features.
> >>
> >> The use case is when you have boot features that requires
> another boot features to start or a specific order.
> >>
> >> The stage allows you to "force" the installation of some
> features before others.
> >>
> >> featuresBoot=(A,B),C,D
> >>
> >> We are "sure" that A and B are completely installed before
> installing C and D features.
> >>
> >> Classic example is wrap: if you need wrap in your feature, you
> have to install wrap before your feature, so you put wrap in the
> first stage.
> >>
> >> Regards
> >> JB
> >>
> >> On 13/09/2021 17:24, Stefan Günst wrote:
> >>> Hi JB,
> >>> thank you very much!
> >>>
> >>>> The same applies with stage:
> >>> That is very interesting and i think we dont know the possibility!
> >>> Can you give us a hint/link how to control this in a real scenario?
> >>> Regards
> >>> Stefan
> >>>> Am 13.09.2021 um 14:07 schrieb Jean-Baptiste Onofré
> <jb@nanthrax.net <ma...@nanthrax.net>>:
> >>>>
> >>>> Hi Stefan,
> >>>>
> >>>> sorry, I missed your message.
> >>>>
> >>>> By default, the boot features are started in sequence (sync)
> meaning:
> >>>>
> >>>> featuresBoot=A,B,C
> >>>>
> >>>> means first A will be installed, and then, once A is
> completely installed, B will be installed, etc
> >>>>
> >>>> The same applies with stage:
> >>>>
> >>>> featuresBoot=(A,C),B
> >>>>
> >>>> so, A will be installed then C, then once A and C are fully
> installed, B will be installed.
> >>>>
> >>>> In async mode, A,B,C will be installed in parallel and the
> resolver will try to find the optimal order.
> >>>> The purpose is to speed up the startup but it's "less"
> predictable.
> >>>>
> >>>> Regards
> >>>> JB
> >>>>
> >>>> On 31/08/2021 16:00, Stefan Günst wrote:
> >>>>> Hi,
> >>>>> no one can comment ?
> >>>>>> Am 18.08.2021 um 17:19 schrieb Stefan Günst
> <stefan.guenst@me.com <ma...@me.com>>:
> >>>>>>
> >>>>>> Hello,
> >>>>>>
> >>>>>> can anyone explain what this is for/what it does and why it
> is default = false.
> >>>>>> We have situations where it helps to start our distribution
> without any errors if we set this to „true“ in
> org.apache.karaf.features.cfg
> >>>>>>
> >>>>>> Any risk to set it to true?
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> Stefan
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >
>
Re: Significance of featuresBootAsynchronous - can you explain?
Posted by Steven Huypens <st...@gmail.com>.
Hi JB,
I could not find how to implement such a 'stage' using the <bootFeatures>
from the karaf-maven-plugin. Do you know where I can find an example ?
Kind regards,
Steven
On Mon, Sep 13, 2021 at 6:22 PM Jean-Baptiste Onofre <jb...@nanthrax.net>
wrote:
> Exactly, you are in the case where stage can help ;)
>
> Regards
> JB
>
> > Le 13 sept. 2021 à 18:06, Stefan Günst <st...@me.com> a écrit :
> >
> > Hi JB,
> >
> > so the strict order of features guarantees that (in sync mode the
> default).
> > That is how we do it at the moment.
> >
> > But: we got situation sometimes on slow systems clean start where we
> start feature „war“ and than later the webapp that needed this but got
> error unknown protocol „war“ …
> >
> > Regards
> >
> > Stefan
> >
> >
> >
> >
> >> Am 13.09.2021 um 17:50 schrieb Jean-Baptiste Onofré <jb...@nanthrax.net>:
> >>
> >> Hi Stefan,
> >>
> >> I guess you mean stage in boot features.
> >>
> >> The use case is when you have boot features that requires another boot
> features to start or a specific order.
> >>
> >> The stage allows you to "force" the installation of some features
> before others.
> >>
> >> featuresBoot=(A,B),C,D
> >>
> >> We are "sure" that A and B are completely installed before installing C
> and D features.
> >>
> >> Classic example is wrap: if you need wrap in your feature, you have to
> install wrap before your feature, so you put wrap in the first stage.
> >>
> >> Regards
> >> JB
> >>
> >> On 13/09/2021 17:24, Stefan Günst wrote:
> >>> Hi JB,
> >>> thank you very much!
> >>>
> >>>> The same applies with stage:
> >>> That is very interesting and i think we dont know the possibility!
> >>> Can you give us a hint/link how to control this in a real scenario?
> >>> Regards
> >>> Stefan
> >>>> Am 13.09.2021 um 14:07 schrieb Jean-Baptiste Onofré <jb@nanthrax.net
> >:
> >>>>
> >>>> Hi Stefan,
> >>>>
> >>>> sorry, I missed your message.
> >>>>
> >>>> By default, the boot features are started in sequence (sync) meaning:
> >>>>
> >>>> featuresBoot=A,B,C
> >>>>
> >>>> means first A will be installed, and then, once A is completely
> installed, B will be installed, etc
> >>>>
> >>>> The same applies with stage:
> >>>>
> >>>> featuresBoot=(A,C),B
> >>>>
> >>>> so, A will be installed then C, then once A and C are fully
> installed, B will be installed.
> >>>>
> >>>> In async mode, A,B,C will be installed in parallel and the resolver
> will try to find the optimal order.
> >>>> The purpose is to speed up the startup but it's "less" predictable.
> >>>>
> >>>> Regards
> >>>> JB
> >>>>
> >>>> On 31/08/2021 16:00, Stefan Günst wrote:
> >>>>> Hi,
> >>>>> no one can comment ?
> >>>>>> Am 18.08.2021 um 17:19 schrieb Stefan Günst <st...@me.com>:
> >>>>>>
> >>>>>> Hello,
> >>>>>>
> >>>>>> can anyone explain what this is for/what it does and why it is
> default = false.
> >>>>>> We have situations where it helps to start our distribution without
> any errors if we set this to „true“ in org.apache.karaf.features.cfg
> >>>>>>
> >>>>>> Any risk to set it to true?
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> Stefan
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >
>
>
Re: Significance of featuresBootAsynchronous - can you explain?
Posted by Jean-Baptiste Onofre <jb...@nanthrax.net>.
Exactly, you are in the case where stage can help ;)
Regards
JB
> Le 13 sept. 2021 à 18:06, Stefan Günst <st...@me.com> a écrit :
>
> Hi JB,
>
> so the strict order of features guarantees that (in sync mode the default).
> That is how we do it at the moment.
>
> But: we got situation sometimes on slow systems clean start where we start feature „war“ and than later the webapp that needed this but got error unknown protocol „war“ …
>
> Regards
>
> Stefan
>
>
>
>
>> Am 13.09.2021 um 17:50 schrieb Jean-Baptiste Onofré <jb...@nanthrax.net>:
>>
>> Hi Stefan,
>>
>> I guess you mean stage in boot features.
>>
>> The use case is when you have boot features that requires another boot features to start or a specific order.
>>
>> The stage allows you to "force" the installation of some features before others.
>>
>> featuresBoot=(A,B),C,D
>>
>> We are "sure" that A and B are completely installed before installing C and D features.
>>
>> Classic example is wrap: if you need wrap in your feature, you have to install wrap before your feature, so you put wrap in the first stage.
>>
>> Regards
>> JB
>>
>> On 13/09/2021 17:24, Stefan Günst wrote:
>>> Hi JB,
>>> thank you very much!
>>>
>>>> The same applies with stage:
>>> That is very interesting and i think we dont know the possibility!
>>> Can you give us a hint/link how to control this in a real scenario?
>>> Regards
>>> Stefan
>>>> Am 13.09.2021 um 14:07 schrieb Jean-Baptiste Onofré <jb...@nanthrax.net>:
>>>>
>>>> Hi Stefan,
>>>>
>>>> sorry, I missed your message.
>>>>
>>>> By default, the boot features are started in sequence (sync) meaning:
>>>>
>>>> featuresBoot=A,B,C
>>>>
>>>> means first A will be installed, and then, once A is completely installed, B will be installed, etc
>>>>
>>>> The same applies with stage:
>>>>
>>>> featuresBoot=(A,C),B
>>>>
>>>> so, A will be installed then C, then once A and C are fully installed, B will be installed.
>>>>
>>>> In async mode, A,B,C will be installed in parallel and the resolver will try to find the optimal order.
>>>> The purpose is to speed up the startup but it's "less" predictable.
>>>>
>>>> Regards
>>>> JB
>>>>
>>>> On 31/08/2021 16:00, Stefan Günst wrote:
>>>>> Hi,
>>>>> no one can comment ?
>>>>>> Am 18.08.2021 um 17:19 schrieb Stefan Günst <st...@me.com>:
>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> can anyone explain what this is for/what it does and why it is default = false.
>>>>>> We have situations where it helps to start our distribution without any errors if we set this to „true“ in org.apache.karaf.features.cfg
>>>>>>
>>>>>> Any risk to set it to true?
>>>>>>
>>>>>>
>>>>>>
>>>>>> Stefan
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>
Re: Significance of featuresBootAsynchronous - can you explain?
Posted by Stefan Günst <st...@me.com>.
Hi JB,
so the strict order of features guarantees that (in sync mode the default).
That is how we do it at the moment.
But: we got situation sometimes on slow systems clean start where we start feature „war“ and than later the webapp that needed this but got error unknown protocol „war“ …
Regards
Stefan
> Am 13.09.2021 um 17:50 schrieb Jean-Baptiste Onofré <jb...@nanthrax.net>:
>
> Hi Stefan,
>
> I guess you mean stage in boot features.
>
> The use case is when you have boot features that requires another boot features to start or a specific order.
>
> The stage allows you to "force" the installation of some features before others.
>
> featuresBoot=(A,B),C,D
>
> We are "sure" that A and B are completely installed before installing C and D features.
>
> Classic example is wrap: if you need wrap in your feature, you have to install wrap before your feature, so you put wrap in the first stage.
>
> Regards
> JB
>
> On 13/09/2021 17:24, Stefan Günst wrote:
>> Hi JB,
>> thank you very much!
>>
>>> The same applies with stage:
>> That is very interesting and i think we dont know the possibility!
>> Can you give us a hint/link how to control this in a real scenario?
>> Regards
>> Stefan
>>> Am 13.09.2021 um 14:07 schrieb Jean-Baptiste Onofré <jb...@nanthrax.net>:
>>>
>>> Hi Stefan,
>>>
>>> sorry, I missed your message.
>>>
>>> By default, the boot features are started in sequence (sync) meaning:
>>>
>>> featuresBoot=A,B,C
>>>
>>> means first A will be installed, and then, once A is completely installed, B will be installed, etc
>>>
>>> The same applies with stage:
>>>
>>> featuresBoot=(A,C),B
>>>
>>> so, A will be installed then C, then once A and C are fully installed, B will be installed.
>>>
>>> In async mode, A,B,C will be installed in parallel and the resolver will try to find the optimal order.
>>> The purpose is to speed up the startup but it's "less" predictable.
>>>
>>> Regards
>>> JB
>>>
>>> On 31/08/2021 16:00, Stefan Günst wrote:
>>>> Hi,
>>>> no one can comment ?
>>>>> Am 18.08.2021 um 17:19 schrieb Stefan Günst <st...@me.com>:
>>>>>
>>>>> Hello,
>>>>>
>>>>> can anyone explain what this is for/what it does and why it is default = false.
>>>>> We have situations where it helps to start our distribution without any errors if we set this to „true“ in org.apache.karaf.features.cfg
>>>>>
>>>>> Any risk to set it to true?
>>>>>
>>>>>
>>>>>
>>>>> Stefan
>>>>>
>>>>>
>>>>>
>>>>>
Re: Significance of featuresBootAsynchronous - can you explain?
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Stefan,
I guess you mean stage in boot features.
The use case is when you have boot features that requires another boot
features to start or a specific order.
The stage allows you to "force" the installation of some features before
others.
featuresBoot=(A,B),C,D
We are "sure" that A and B are completely installed before installing C
and D features.
Classic example is wrap: if you need wrap in your feature, you have to
install wrap before your feature, so you put wrap in the first stage.
Regards
JB
On 13/09/2021 17:24, Stefan Günst wrote:
> Hi JB,
>
> thank you very much!
>
>
>> The same applies with stage:
> That is very interesting and i think we dont know the possibility!
>
> Can you give us a hint/link how to control this in a real scenario?
>
> Regards
> Stefan
>
>
>
>
>> Am 13.09.2021 um 14:07 schrieb Jean-Baptiste Onofré <jb...@nanthrax.net>:
>>
>> Hi Stefan,
>>
>> sorry, I missed your message.
>>
>> By default, the boot features are started in sequence (sync) meaning:
>>
>> featuresBoot=A,B,C
>>
>> means first A will be installed, and then, once A is completely installed, B will be installed, etc
>>
>> The same applies with stage:
>>
>> featuresBoot=(A,C),B
>>
>> so, A will be installed then C, then once A and C are fully installed, B will be installed.
>>
>> In async mode, A,B,C will be installed in parallel and the resolver will try to find the optimal order.
>> The purpose is to speed up the startup but it's "less" predictable.
>>
>> Regards
>> JB
>>
>> On 31/08/2021 16:00, Stefan Günst wrote:
>>> Hi,
>>> no one can comment ?
>>>> Am 18.08.2021 um 17:19 schrieb Stefan Günst <st...@me.com>:
>>>>
>>>> Hello,
>>>>
>>>> can anyone explain what this is for/what it does and why it is default = false.
>>>> We have situations where it helps to start our distribution without any errors if we set this to „true“ in org.apache.karaf.features.cfg
>>>>
>>>> Any risk to set it to true?
>>>>
>>>>
>>>>
>>>> Stefan
>>>>
>>>>
>>>>
>>>>
>
Re: Significance of featuresBootAsynchronous - can you explain?
Posted by Stefan Günst <st...@me.com>.
Hi JB,
thank you very much!
> The same applies with stage:
That is very interesting and i think we dont know the possibility!
Can you give us a hint/link how to control this in a real scenario?
Regards
Stefan
> Am 13.09.2021 um 14:07 schrieb Jean-Baptiste Onofré <jb...@nanthrax.net>:
>
> Hi Stefan,
>
> sorry, I missed your message.
>
> By default, the boot features are started in sequence (sync) meaning:
>
> featuresBoot=A,B,C
>
> means first A will be installed, and then, once A is completely installed, B will be installed, etc
>
> The same applies with stage:
>
> featuresBoot=(A,C),B
>
> so, A will be installed then C, then once A and C are fully installed, B will be installed.
>
> In async mode, A,B,C will be installed in parallel and the resolver will try to find the optimal order.
> The purpose is to speed up the startup but it's "less" predictable.
>
> Regards
> JB
>
> On 31/08/2021 16:00, Stefan Günst wrote:
>> Hi,
>> no one can comment ?
>>> Am 18.08.2021 um 17:19 schrieb Stefan Günst <st...@me.com>:
>>>
>>> Hello,
>>>
>>> can anyone explain what this is for/what it does and why it is default = false.
>>> We have situations where it helps to start our distribution without any errors if we set this to „true“ in org.apache.karaf.features.cfg
>>>
>>> Any risk to set it to true?
>>>
>>>
>>>
>>> Stefan
>>>
>>>
>>>
>>>
Re: Significance of featuresBootAsynchronous - can you explain?
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Stefan,
sorry, I missed your message.
By default, the boot features are started in sequence (sync) meaning:
featuresBoot=A,B,C
means first A will be installed, and then, once A is completely
installed, B will be installed, etc
The same applies with stage:
featuresBoot=(A,C),B
so, A will be installed then C, then once A and C are fully installed, B
will be installed.
In async mode, A,B,C will be installed in parallel and the resolver will
try to find the optimal order.
The purpose is to speed up the startup but it's "less" predictable.
Regards
JB
On 31/08/2021 16:00, Stefan Günst wrote:
> Hi,
>
> no one can comment ?
>
>
>> Am 18.08.2021 um 17:19 schrieb Stefan Günst <st...@me.com>:
>>
>> Hello,
>>
>> can anyone explain what this is for/what it does and why it is default = false.
>> We have situations where it helps to start our distribution without any errors if we set this to „true“ in org.apache.karaf.features.cfg
>>
>> Any risk to set it to true?
>>
>>
>>
>> Stefan
>>
>>
>>
>>
>
Re: Significance of featuresBootAsynchronous - can you explain?
Posted by Stefan Günst <st...@me.com>.
Hi,
no one can comment ?
> Am 18.08.2021 um 17:19 schrieb Stefan Günst <st...@me.com>:
>
> Hello,
>
> can anyone explain what this is for/what it does and why it is default = false.
> We have situations where it helps to start our distribution without any errors if we set this to „true“ in org.apache.karaf.features.cfg
>
> Any risk to set it to true?
>
>
>
> Stefan
>
>
>
>