[KARAF-5371] Race condition between FeatureService and Fileinstall

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 4.1.2
• Fix Version/s: 4.1.3, 4.2.0.M1
• Component/s: karaf
• Assignee: Guillaume Nodet
• Reporter: J. Brébec
• Created: 12/Sep/17 14:32
• Updated: 14/Sep/18 15:13
• Resolved: 16/Oct/17 18:48

Description

If a bundle is installed when the FeatureService is started, then it is possible that this bundle is not associated to the default region. as a consequence, every services exported by this bundle are not visible from the osgi container, until karaf is restarted.

A real usecase :

• A new karaf distribution, with a blueprint file in a folder managed by fileinstall ;
• When the distribution is started, as fileinstall is started before the feature bundle, and the folder are watched asynchronously, the blueprint file is installed before or in the same time the featureservice is started
  => the services exported by the blueprint file are not visible

This race condition is located in the FeatureService activator : the digraph is loaded, and every bundle not known are added to the default region. then, it subscribes a bundle-listener : If a bundle X is installed between the digraph loading and the subscription of the bundle listener, then this bundle X is not attached to the default region.

On my machine, this issue happens 70% of the time on a cold start.

Issue Links

• links to: GitHub Pull Request #373