[jira] [Resolved] (KARAF-4066) Features command bundle should recover if FeatureService unavailable initially

["Jonathan Anstey (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KARAF-4066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Anstey resolved KARAF-4066.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 3.0.6
                   4.0.3
                   2.4.4

[janstey@bender features]$ git push origin 
Counting objects: 15, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (15/15), done.
Writing objects: 100% (15/15), 2.04 KiB | 0 bytes/s, done.
Total 15 (delta 6), reused 0 (delta 0)
To https://git-wip-us.apache.org/repos/asf/karaf.git
   f491fc7..7d16949  karaf-2.x -> karaf-2.x
   74692ad..4b0bea9  karaf-3.0.x -> karaf-3.0.x
   9167d3d..cf84f16  master -> master


> 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
>             Fix For: 2.4.4, 4.0.3, 3.0.6
>
>
> 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)