[
https://issues.apache.org/jira/browse/FELIX-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Hull updated FELIX-4740:
----------------------------
Description:
In working with FileInstall, I've discovered an odd condition under which
bundles installed by FileInstall will never be started, even though their start
level is reached. This seems to happen most frequently when the active level is
set to a value less than the start level.
In that case, the initial scan will install bundles in the deploy directory,
but not start them. That is expected. However, once the required start level is
reached, the installed bundles are only started if a BundleEvent is fired after
the start level change. Otherwise, the stateChanged flag in FileInstall will
not be set, and we will never start the installed bundles.
was:
In working with FileInstall, I've discovered an odd condition under which
bundles installed by FileInstall will never be started, even though their start
level is reached. This seems to happen most frequently when the active level is
set to a value less than the start level.
In that case, the initial scan will install bundles in the deploy directory,
but not start them. That is expected. However, once the required start level is
reached, the installed bundles are only started if a BundleEvent is fired after
the start level change. Otherwise, the stateChanged flag in FileInstall will
not be set, and we will never start the installed bundles.
At least in persistent mode, it would seem more logical for FileInstall to call
start() on each bundle regardless of start level and let the framework
autostart them. Alternatively, just make sure start() is called on bundles once
their start level is reached...
> Bundles don't start if no BundleEvent fired after reaching start level
> ----------------------------------------------------------------------
>
> Key: FELIX-4740
> URL: https://issues.apache.org/jira/browse/FELIX-4740
> Project: Felix
> Issue Type: Bug
> Components: File Install
> Affects Versions: fileinstall-3.4.2
> Environment: Mac OS X 10.10, Apache Karaf 3.0.2
> Reporter: Tim Hull
>
> In working with FileInstall, I've discovered an odd condition under which
> bundles installed by FileInstall will never be started, even though their
> start level is reached. This seems to happen most frequently when the active
> level is set to a value less than the start level.
> In that case, the initial scan will install bundles in the deploy directory,
> but not start them. That is expected. However, once the required start level
> is reached, the installed bundles are only started if a BundleEvent is fired
> after the start level change. Otherwise, the stateChanged flag in FileInstall
> will not be set, and we will never start the installed bundles.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
