Have you tried restarting the framework? That should result in the
STARTING subsystem being in the RESOLVED state. You should then be
able to use the web console to uninstall it. If you're able to
ascertain what's causing your subsystem to get stuck in the STARTING
state and feel that it's a bug, please open a JIRA at
https://issues.apache.org/jira/browse/ARIES.

On Mon, Nov 16, 2015 at 10:32 AM, Anja Gruss <[email protected]> wrote:
> Hi there,
>
> I managed to have a subsystem bundle, that is faulty but desperately trying
> to start. I cannot uninstall it via the web console plugin.
>
> Error Log says
>
>
> *ERROR* [Thread-66]
> org.apache.sling.extensions.threaddump.internal.Activator Uncaught exception
> in Thread Thread[Thread-66,5,Configuration Admin Service]
> org.osgi.service.subsystem.SubsystemException: Operation timed out while
> waiting for the subsystem to change state from STARTING
> at
> org.apache.aries.subsystem.core.internal.AbstractAction.waitForStateChange(AbstractAction.java:59)
> at
> org.apache.aries.subsystem.core.internal.UninstallAction.run(UninstallAction.java:33)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.apache.aries.subsystem.core.internal.BasicSubsystem.uninstall(BasicSubsystem.java:310)
> at
> org.apache.felix.webconsole.plugins.subsystem.internal.WebConsolePlugin$4.exec(WebConsolePlugin.java:243)
> at
> org.apache.felix.webconsole.plugins.subsystem.internal.WebConsolePlugin$5.run(WebConsolePlugin.java:267)
> at java.lang.Thread.run(Thread.java:745)
>
>
> Trying to overwrite it with a newer version of the subsystem results in
> another exception
>
> org.apache.sling.extensions.threaddump.internal.Activator Uncaught exception
> in Thread Thread[Thread-72,5,Configuration Admin Service]
> org.osgi.service.subsystem.SubsystemException:
> org.osgi.service.resolver.ResolutionException: Uses constraint violation.
> Unable to resolve resource ...
> [/var/folders/zz/zyxvpxvq6csfxvn_n00002680000jk/T/inputStreamExtract5852547367619201406.zip/....jar]
> because it is exposed to package 'javax.imageio.metadata' from resources
> org.apache.felix.framework [0] and org.apache.felix.framework [0] via two
> dependency chains.
>
> Is there another way to forcefully remove the offending bundle?
>
> Thanks in advance
>
> /anja
>
>

Reply via email to