You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jonathan Anstey (JIRA)" <ji...@apache.org> on 2015/10/14 20:13:05 UTC
[jira] [Created] (KARAF-4066) Features command bundle should
recover if FeatureService unavailable initially
Jonathan Anstey created KARAF-4066:
--------------------------------------
Summary: Features command bundle should recover if FeatureService unavailable initially
Key: KARAF-4066
URL: https://issues.apache.org/jira/browse/KARAF-4066
Project: Karaf
Issue Type: Bug
Affects Versions: 2.4.2
Reporter: Jonathan Anstey
Assignee: Jonathan Anstey
If the FeaturesService is unavailable during startup for some reason, after 5 minutes, you will get a TimeoutException from blueprint and the bundle goes into a failed state. If FeaturesService then becomes available, the features command bundle does not recover.
I think blueprint.graceperiod:=false is a good workaround to this. The user will see "FeaturesService service is unavailable" when issuing features commands rather than not being able to use them at all. Then when the feature is back the command operates normally.
There is a similar issue described in KARAF-1925.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)