]
Thomas Diesler updated AS7-858:
-------------------------------
Summary: Cannot load module when applying resolver results (was: Exception when
deploying OSGi bundle)
Cannot load module when applying resolver results
-------------------------------------------------
Key: AS7-858
URL:
https://issues.jboss.org/browse/AS7-858
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: 7.0.0.CR1
Reporter: David Bosschaert
Assignee: Thomas Diesler
This was observed on
git://github.com/jbosgi/jboss-as.git on the jbosgi branch just on 20
May at 0730 UTC.
Deploying a simple OSGi bundle using the hotdeploy directory into AS7 causes an
exception. The bundle is deployed straight after startup. It doesn't seem to happen
every time...
08:31:04,136 INFO [org.jboss.osgi.framework.internal.FrameworkActive] (MSC service
thread 1-4) OSGi Framework started
08:31:04,136 INFO [org.jboss.as.osgi] (MSC service thread 1-3) Installing deployment:
[TestBundle:1.0.0.201105200821,location=TestBundle_1.0.0.201105200821.jar]
08:31:04,141 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread
1-3) Install bundle: TestBundle:1.0.0.201105200821
08:31:04,144 ERROR [org.jboss.msc.service] (MSC service thread 1-2) MSC00002: Invocation
of listener "org.jboss.as.osgi.deployment.BundleStartTracker$1@1c10834" failed:
java.lang.IllegalStateException: Cannot load module:
deployment.TestBundle:1.0.0.201105200821
at
org.jboss.osgi.framework.internal.ResolverPlugin.loadModules(ResolverPlugin.java:261)
at
org.jboss.osgi.framework.internal.ResolverPlugin.applyResolverResults(ResolverPlugin.java:229)
at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:161)
at
org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:555)
at
org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:205)
at
org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:499)
at
org.jboss.as.osgi.deployment.BundleStartTracker$1.processService(BundleStartTracker.java:135)
at
org.jboss.as.osgi.deployment.BundleStartTracker$1.serviceStarted(BundleStartTracker.java:107)
at
org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1322)
[jboss-msc-1.0.0.Beta8.jar:1.0.0.Beta8]
at
org.jboss.msc.service.ServiceControllerImpl.access$2600(ServiceControllerImpl.java:47)
[jboss-msc-1.0.0.Beta8.jar:1.0.0.Beta8]
at
org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1850)
[jboss-msc-1.0.0.Beta8.jar:1.0.0.Beta8]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_23]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_23]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_23]
Caused by: org.jboss.modules.ModuleNotFoundException:
deployment.TestBundle:1.0.0.201105200821
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:158) [:1.0.0.CR2]
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:152) [:1.0.0.CR2]
at
org.jboss.osgi.framework.internal.ModuleManagerPlugin.loadModule(ModuleManagerPlugin.java:561)
at
org.jboss.osgi.framework.internal.ResolverPlugin.loadModules(ResolverPlugin.java:259)
... 13 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: