sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konrad Windszus (JIRA)" <>
Subject [jira] [Commented] (SLING-5457) OsgiInstaller should retry to start bundles on failures
Date Wed, 15 Feb 2017 15:00:47 GMT


Konrad Windszus commented on SLING-5457:

I created a follow-up ticket for the more global improvement of exception/retry handling in

> OsgiInstaller should retry to start bundles on failures
> -------------------------------------------------------
>                 Key: SLING-5457
>                 URL:
>             Project: Sling
>          Issue Type: Bug
>          Components: Installer
>    Affects Versions: Installer Core 3.6.4
>            Reporter: Jörg Hoh
> The OsgiInstaller doesn't update a bundle properly, if there's an exception from the
> I have this exception:
> {code}
> 11.12.2015 14:09:36.753 *INFO* [FelixStartLevel] my.custom.bundle BundleEvent RESOLVED
> 11.12.2015 14:09:36.753 *INFO* [FelixStartLevel] my.custom.bundle BundleEvent STARTING
> 11.12.2015 14:09:36.754 INFO [OsgiInstallerImpl]
Removing failing update task - unable to retry: BundleUpdateTask: TaskResource(url=jcrinstall:/apps/myapp/install/my.custom.bundle-1.5.6-SNAPSHOT.jar,
entity=bundle:my.custom.bundle, state=INSTALL, attributes=[,
Bundle-SymbolicName=my.custom.bundle, Bundle-Version=1.5.6-SNAPSHOT], digest=1449838063263)
> org.osgi.framework.BundleException: Bundle my.custom.bundle [252] cannot be update, since
it is either starting or stopping.
> at org.apache.felix.framework.Felix.updateBundle(
> at org.apache.felix.framework.BundleImpl.update(
> at
> at
> at
> at
> at
> {code}
> I don't know for what reason the Felix.updateBundle() failed (see also FELIX-5138 to
get some more information in this case), but from my point of view there should be a dedicated
error handling just for the {code}BundleImpl.update{code} call. Does it make sense to retry
the installation at a later point in time (maybe 3 times at max)?
> (I got this exception when I deployed a large number of bundles through the JCR installer.
It happens only once in a while, but it's an annoying task to fix it manually.)

This message was sent by Atlassian JIRA

View raw message