I have trying this with no result
<Bundle-SymbolicName>${project.artifactId};blueprint.timeout=10000</Bundle-SymbolicName>
when i'm running bundle:stop xxx i still see the warn message in my logs ( WARN
[pipe-stop 103] Error occurred while stopping lifecycle strategies. This
exception will be
ignored.org.osgi.service.blueprint.container.NoSuchComponentException: No
component with id 'blueprintBundle' could be found)
I also see this blueprint.timeout=10000 have no effect my bundle stop immediatly
Michael.
________________________________
De : Jean-Baptiste Onofre <[email protected]>
Envoyé : mercredi 2 décembre 2020 16:20
À : [email protected] <[email protected]>
Objet : Re: org.osgi.service.blueprint.container.NoSuchComponentException: No
component with id 'blueprintBundle' could be found
OK. You have to reduce the timeout (grace period) on the camel shutdown
strategy or increase blueprint timeout.
Did you try this ?
Regards
JB
Le 2 déc. 2020 à 16:11, michael e
<[email protected]<mailto:[email protected]>> a écrit :
I wasn't aware about this timeout configuration (is not a simple service but a
camel context)
Michael.
________________________________
De : michael e <[email protected]<mailto:[email protected]>>
Envoyé : mercredi 2 décembre 2020 16:04
À : [email protected]<mailto:[email protected]>
<[email protected]<mailto:[email protected]>>
Objet : RE: org.osgi.service.blueprint.container.NoSuchComponentException: No
component with id 'blueprintBundle' could be found
Hello JB,
Thanks for your response, i'm sorry i poste the wrong camel ticket (by the way
i think claus already take care about this issue).
The ticket https://issues.apache.org/jira/browse/CAMEL-15760
Michael.
________________________________
De : Jean-Baptiste Onofre <[email protected]<mailto:[email protected]>>
Envoyé : mercredi 2 décembre 2020 16:00
À : [email protected]<mailto:[email protected]>
<[email protected]<mailto:[email protected]>>
Objet : Re: org.osgi.service.blueprint.container.NoSuchComponentException: No
component with id 'blueprintBundle' could be found
Hmm, it seems a mistake in the configuration between the blueprint timeout and
the Camel Shutdown strategy, no ?
Do you consider this as a bug ?
Regards
JB
Le 2 déc. 2020 à 15:01, michael e
<[email protected]<mailto:[email protected]>> a écrit :
Hello,
When i stop camel bundle using blueprint i get this
org.osgi.service.blueprint.container.NoSuchComponentException: No component
with id 'blueprintBundle' could be found
Karaf version is 4.3.0
camel-blueprint is 3.1.0
Related discussion:
https://issues.apache.org/jira/browse/CAMEL-14332
[CAMEL-14332] camel-blueprint - Camel route does not consider the value of
ShutdownStrategy timeout. - ASF
JIRA<https://issues.apache.org/jira/browse/CAMEL-14332>
So when the Shutdown strategy timeout is longer than one minute, the
BlueprintEventDispatcher timeout is triggered for first, making the shutdown
strategy useless.. The solution to this, is to remove the piece of code that
handle the destroy event from BlueprintCamelContext.
issues.apache.org<http://issues.apache.org/>
Regards,
Michael.
