[JBoss JIRA] Created: (JBOSGI-476) Cannot acquire start/stop lock upon Equinox Util Bundle deployment
8:02 a.m.
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
8:04 a.m.
New subject: [JBoss JIRA] Updated: (JBOSGI-476) Cannot acquire start/stop lock upon Equinox Util Bundle deployment
[
https://issues.jboss.org/browse/JBOSGI-476?page=com.atlassian.jira.plugin...
]
Jacek Laskowski updated JBOSGI-476:
-----------------------------------
Attachment: Equinox Util Bundle in the osgi web console.jpg
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
Attachments: Equinox Util Bundle in the osgi web console.jpg
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
8:14 a.m.
New subject: [JBoss JIRA] Commented: (JBOSGI-476) Cannot acquire start/stop lock upon Equinox Util Bundle deployment
[
https://issues.jboss.org/browse/JBOSGI-476?page=com.atlassian.jira.plugin...
]
Thomas Diesler commented on JBOSGI-476:
---------------------------------------
Could you attach the bundle to this issue?
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
Attachments: Equinox Util Bundle in the osgi web console.jpg
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
8:18 a.m.
New subject: [JBoss JIRA] Updated: (JBOSGI-476) Cannot acquire start/stop lock upon Equinox Util Bundle deployment
[
https://issues.jboss.org/browse/JBOSGI-476?page=com.atlassian.jira.plugin...
]
Thomas Diesler updated JBOSGI-476:
----------------------------------
Fix Version/s: JBossOSGi 1.0.0
Component/s: Core Framework
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)
Components: Core Framework
Reporter: Jacek Laskowski
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.0.0
Attachments: Equinox Util Bundle in the osgi web console.jpg
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
8:46 a.m.
New subject: [JBoss JIRA] Updated: (JBOSGI-476) Cannot acquire start/stop lock upon Equinox Util Bundle deployment
[
https://issues.jboss.org/browse/JBOSGI-476?page=com.atlassian.jira.plugin...
]
Jacek Laskowski updated JBOSGI-476:
-----------------------------------
Attachment: org.eclipse.equinox.util_1.0.300.v20110502.jar
The bundle
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)
Components: Core Framework
Reporter: Jacek Laskowski
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.0.0
Attachments: Equinox Util Bundle in the osgi web console.jpg,
org.eclipse.equinox.util_1.0.300.v20110502.jar
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
8:55 a.m.
New subject: [JBoss JIRA] Commented: (JBOSGI-476) Cannot acquire start/stop lock upon Equinox Util Bundle deployment
[
https://issues.jboss.org/browse/JBOSGI-476?page=com.atlassian.jira.plugin...
]
Thomas Diesler commented on JBOSGI-476:
---------------------------------------
First issue I see is JBOSGI-476
Cannot start bundle: org.eclipse.equinox.util:1.0.300.v20110502:
org.osgi.framework.BundleException: Unsupported execution environment [OSGi/Minimum-1.1]
we have [OSGi/Minimum-1.2, , J2SE-1.2, , J2SE-1.3, , J2SE-1.4, , J2SE-1.5, , JavaSE-1.6]
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)
Components: Core Framework
Reporter: Jacek Laskowski
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.0.0
Attachments: Equinox Util Bundle in the osgi web console.jpg,
org.eclipse.equinox.util_1.0.300.v20110502.jar
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
9:08 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBOSGI-476) Cannot acquire start/stop lock upon Equinox Util Bundle deployment
[
https://issues.jboss.org/browse/JBOSGI-476?page=com.atlassian.jira.plugin...
]
Thomas Diesler edited comment on JBOSGI-476 at 7/6/11 10:07 AM:
----------------------------------------------------------------
First issue I see is JBOSGI-477
Cannot start bundle: org.eclipse.equinox.util:1.0.300.v20110502:
org.osgi.framework.BundleException: Unsupported execution environment [OSGi/Minimum-1.1]
we have [OSGi/Minimum-1.2, , J2SE-1.2, , J2SE-1.3, , J2SE-1.4, , J2SE-1.5, , JavaSE-1.6]
was (Author: thomas.diesler):
First issue I see is JBOSGI-476
Cannot start bundle: org.eclipse.equinox.util:1.0.300.v20110502:
org.osgi.framework.BundleException: Unsupported execution environment [OSGi/Minimum-1.1]
we have [OSGi/Minimum-1.2, , J2SE-1.2, , J2SE-1.3, , J2SE-1.4, , J2SE-1.5, , JavaSE-1.6]
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)
Components: Core Framework
Reporter: Jacek Laskowski
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.0.0
Attachments: Equinox Util Bundle in the osgi web console.jpg,
org.eclipse.equinox.util_1.0.300.v20110502.jar
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
12:08 p.m.
New subject: [JBoss JIRA] Work started: (JBOSGI-476) Cannot acquire start/stop lock upon Equinox Util Bundle deployment
[
https://issues.jboss.org/browse/JBOSGI-476?page=com.atlassian.jira.plugin...
]
Work on JBOSGI-476 started by Thomas Diesler.
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)
Components: Core Framework
Reporter: Jacek Laskowski
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.0.0
Attachments: Equinox Util Bundle in the osgi web console.jpg,
org.eclipse.equinox.util_1.0.300.v20110502.jar
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
1:01 p.m.
New subject: [JBoss JIRA] Updated: (JBOSGI-476) Cannot acquire start/stop lock for lazy bundles
[
https://issues.jboss.org/browse/JBOSGI-476?page=com.atlassian.jira.plugin...
]
Thomas Diesler updated JBOSGI-476:
----------------------------------
Summary: Cannot acquire start/stop lock for lazy bundles (was: Cannot acquire
start/stop lock upon Equinox Util Bundle deployment)
Cannot acquire start/stop lock for lazy bundles
-----------------------------------------------
Key: JBOSGI-476
URL: https://issues.jboss.org/browse/JBOSGI-476
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Framework
Reporter: Jacek Laskowski
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.0.0
Attachments: Equinox Util Bundle in the osgi web console.jpg,
org.eclipse.equinox.util_1.0.300.v20110502.jar
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
1:03 p.m.
New subject: [JBoss JIRA] Commented: (JBOSGI-476) Cannot acquire start/stop lock for lazy bundles
[
https://issues.jboss.org/browse/JBOSGI-476?page=com.atlassian.jira.plugin...
]
Thomas Diesler commented on JBOSGI-476:
---------------------------------------
The framework re-enters HostBundleState.startInternal() when a lazy bundle has a
BundleActivator.
Additionally there is AS7-1213
Cannot acquire start/stop lock for lazy bundles
-----------------------------------------------
Key: JBOSGI-476
URL: https://issues.jboss.org/browse/JBOSGI-476
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Framework
Reporter: Jacek Laskowski
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.0.0
Attachments: Equinox Util Bundle in the osgi web console.jpg,
org.eclipse.equinox.util_1.0.300.v20110502.jar
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
1:05 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBOSGI-476) Cannot acquire start/stop lock for lazy bundles
[
https://issues.jboss.org/browse/JBOSGI-476?page=com.atlassian.jira.plugin...
]
Thomas Diesler edited comment on JBOSGI-476 at 7/6/11 2:04 PM:
---------------------------------------------------------------
The framework re-enters HostBundleState.startInternal() when a lazy bundle that has a
BundleActivator is explicitly started. Additionally there is AS7-1213
was (Author: thomas.diesler):
The framework re-enters HostBundleState.startInternal() when a lazy bundle has a
BundleActivator.
Additionally there is AS7-1213
Cannot acquire start/stop lock for lazy bundles
-----------------------------------------------
Key: JBOSGI-476
URL: https://issues.jboss.org/browse/JBOSGI-476
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Framework
Reporter: Jacek Laskowski
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.0.0
Attachments: Equinox Util Bundle in the osgi web console.jpg,
org.eclipse.equinox.util_1.0.300.v20110502.jar
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
1:17 p.m.
New subject: [JBoss JIRA] Resolved: (JBOSGI-476) Cannot acquire start/stop lock for lazy bundles
[
https://issues.jboss.org/browse/JBOSGI-476?page=com.atlassian.jira.plugin...
]
Thomas Diesler resolved JBOSGI-476.
-----------------------------------
Fix Version/s: JBossOSGi 1.0.0 CR1
(was: JBossOSGi 1.0.0)
Resolution: Done
Done
Cannot acquire start/stop lock for lazy bundles
-----------------------------------------------
Key: JBOSGI-476
URL: https://issues.jboss.org/browse/JBOSGI-476
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Framework
Reporter: Jacek Laskowski
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.0.0 CR1
Attachments: Equinox Util Bundle in the osgi web console.jpg,
org.eclipse.equinox.util_1.0.300.v20110502.jar
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
4:12 a.m.
New subject: [JBoss JIRA] Updated: (JBOSGI-476) Cannot acquire start/stop lock for lazy bundles
[
https://issues.jboss.org/browse/JBOSGI-476?page=com.atlassian.jira.plugin...
]
Thomas Diesler updated JBOSGI-476:
----------------------------------
Fix Version/s: Core Framework 1.0.0
(was: JBossOSGi 1.0.0 CR1)
Cannot acquire start/stop lock for lazy bundles
-----------------------------------------------
Key: JBOSGI-476
URL: https://issues.jboss.org/browse/JBOSGI-476
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Framework
Reporter: Jacek Laskowski
Assignee: Thomas Diesler
Fix For: Core Framework 1.0.0
Attachments: Equinox Util Bundle in the osgi web console.jpg,
org.eclipse.equinox.util_1.0.300.v20110502.jar
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
5387
days inactive
5406
days old
jboss-osgi-issues@lists.jboss.org
12 comments
2 participants
participants (2)
-
Jacek Laskowski (JIRA) -
Thomas Diesler (JIRA)