]
Thomas Diesler updated JBOSGI-385:
----------------------------------
Fix Version/s: Approved and Unscheduled
IllegalStateException when deploying & starting a bundle through
web console
----------------------------------------------------------------------------
Key: JBOSGI-385
URL:
https://issues.jboss.org/browse/JBOSGI-385
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Framework, jboss-osgi-webconsole
Affects Versions: JBossOSGi 1.0.0 Beta8
Reporter: David Bosschaert
Assignee: David Bosschaert
Fix For: Approved but Unscheduled
When installing a bundle through the web console and ticking the start tickbox as well,
it often generates an exception (see below). It is probably related to the fact that if
you don't select the start tickbox, the bundle gets started anyway. With the tickbox
enabled it seems like the system is trying to start the bundle twice concurrently.
org.apache.felix.log.LogException: org.osgi.framework.BundleException: Cannot start
bundle: exporting-bundle:0.0.0
at org.jboss.osgi.container.bundle.HostBundle.startInternal(HostBundle.java:239)
at org.jboss.osgi.container.bundle.AbstractBundle.start(AbstractBundle.java:478)
at
org.jboss.osgi.container.plugin.internal.StartLevelPluginImpl$3.run(StartLevelPluginImpl.java:162)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.IllegalStateException: BundleContext already available
at
org.jboss.osgi.container.bundle.AbstractBundle.createBundleContext(AbstractBundle.java:170)
at org.jboss.osgi.container.bundle.HostBundle.startInternal(HostBundle.java:179)
... 5 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: