Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Date: Fri, 10 Feb 2017 12:29:41 +0000 (UTC)
From: "Karl Pauls (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Message-ID: <JIRA.12921664.1450100315000.48214.1486729781661@Atlassian.JIRA>
In-Reply-To: <JIRA.12921664.1450100315000@Atlassian.JIRA>
References: <JIRA.12921664.1450100315000@Atlassian.JIRA> <JIRA.12921664.1450100315923@jira-lw-us.apache.org>
Subject: [jira] [Updated] (FELIX-5138) Felix should log underlying exception
 on failed bundle update
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Fri, 10 Feb 2017 12:29:46 -0000


     [ https://issues.apache.org/jira/browse/FELIX-5138?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Pauls updated FELIX-5138:
------------------------------
    Fix Version/s: framework-5.6.2

> Felix should log underlying exception on failed bundle update
> -------------------------------------------------------------
>
>                 Key: FELIX-5138
>                 URL: https://issues.apache.org/jira/browse/FELIX-5138
>             Project: Felix
>          Issue Type: Improvement
>          Components: Framework
>    Affects Versions: framework-5.0.1
>            Reporter: J=C3=B6rg Hoh
>            Assignee: Karl Pauls
>             Fix For: framework-5.6.2
>
>
> I run an application, which is based on Apache Sling. We recently updated=
 our bundles and I faced this message; as outcome my.custom.bundle wasn't u=
pdated properly.
> {noformat}
> 11.12.2015 14:09:36.753 *INFO* [FelixStartLevel] my.custom.bundle BundleE=
vent RESOLVED
> 11.12.2015 14:09:36.753 *INFO* [FelixStartLevel] my.custom.bundle BundleE=
vent STARTING
> 11.12.2015 14:09:36.754 INFO [OsgiInstallerImpl] org.apache.sling.install=
er.core.impl.tasks.BundleUpdateTask Removing failing update task - unable t=
o retry: BundleUpdateTask: TaskResource(url=3Djcrinstall:/apps/myapp/instal=
l/my.custom.bundle-1.5.6-SNAPSHOT.jar, entity=3Dbundle:my.custom.bundle, st=
ate=3DINSTALL, attributes=3D[org.apache.sling.installer.api.tasks.ResourceT=
ransformer=3D:28:84:15:, Bundle-SymbolicName=3Dmy.custom.bundle, Bundle-Ver=
sion=3D1.5.6-SNAPSHOT], digest=3D1449838063263)
> 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(Felix.java:2311)
> at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:995)
> at org.apache.sling.installer.core.impl.tasks.BundleUpdateTask.execute(Bu=
ndleUpdateTask.java:92)
> at org.apache.sling.installer.core.impl.OsgiInstallerImpl.doExecuteTasks(=
OsgiInstallerImpl.java:847)
> at org.apache.sling.installer.core.impl.OsgiInstallerImpl.executeTasks(Os=
giInstallerImpl.java:689)
> at org.apache.sling.installer.core.impl.OsgiInstallerImpl.run(OsgiInstall=
erImpl.java:265)
> at java.lang.Thread.run(Thread.java:767)
> {noformat}
> According to the code, Felix.updateBundle() prints this message only when=
 acquireBundleLock() throws an IllegalStateException; and this IllegalState=
ment exception can have 2 different causes.
> It would be good, if the log message contains an information, which of th=
ese 2 reasons actually occurred. And it would be even better, if this actio=
n is actually retried, as this problem looks like a temporary issue for me.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)