[jboss-osgi-issues] [JBoss JIRA] Created: (JBOSGI-476) Cannot acquire start/stop lock upon Equinox Util Bundle deployment

[Jacek Laskowski (JIRA)]

Cannot acquire start/stop lock upon Equinox Util Bundle deployment
------------------------------------------------------------------

                 Key: JBOSGI-476
                 URL: https://issues.jboss.org/browse/JBOSGI-476
             Project: JBoss OSGi
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Jacek Laskowski
            Assignee: Thomas Diesler


Although there's the following error reported in the logs, the bundle is in ACTIVE state as shown in the screenshot of the osgi console.

14:52:20,238 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) Starting deployment of "org.eclipse.equinox.util_1.0.300.v20110502.jar"
14:52:20,308 INFO  [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-1) Install bundle: org.eclipse.equinox.util:1.0.300.v20110502
14:52:20,323 INFO  [org.jboss.as.server.controller] (DeploymentScanner-threads - 1) Deployed "org.eclipse.equinox.util_1.0.300.v20110502.jar"
14:52:30,320 ERROR [org.jboss.osgi.framework.internal.LazyActivationTracker] (MSC service thread 1-1) Cannot activate lazily: org.eclipse.equinox.util:1.0.300.v20110502: org.osgi.framework.BundleException: Cannot acquire start/stop lock for: org.eclipse.equinox.util:1.0.300.v20110502
	at org.jboss.osgi.framework.internal.HostBundleState.aquireActivationLock(HostBundleState.java:423)
	at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:194)
	at org.jboss.osgi.framework.internal.HostBundleState.activateLazily(HostBundleState.java:141)
	at org.jboss.osgi.framework.internal.LazyActivationTracker.processActivationStack(LazyActivationTracker.java:95)
	at org.jboss.osgi.framework.internal.LazyActivationTracker.processLoadedClass(LazyActivationTracker.java:52)
	at org.jboss.osgi.framework.internal.HostBundleState.loadClass(HostBundleState.java:151)
	at org.jboss.osgi.framework.internal.HostBundleState.transitionToActive(HostBundleState.java:285)
	at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:217)
	at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494)
	at org.jboss.as.osgi.deployment.BundleStartTracker$1.processService(BundleStartTracker.java:146)
	at org.jboss.as.osgi.deployment.BundleStartTracker$1.transition(BundleStartTracker.java:121)
	at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1442)
	at org.jboss.msc.service.ServiceControllerImpl.access$2500(ServiceControllerImpl.java:49)
	at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1940)
	at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26]
	at java.lang.Thread.run(Thread.java:680) [:1.6.0_26]

14:52:30,405 INFO  [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-1) Bundle started: org.eclipse.equinox.util:1.0.300.v20110502


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira