[
https://issues.jboss.org/browse/AS7-2214?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler edited comment on AS7-2214 at 10/24/11 9:47 AM:
---------------------------------------------------------------
The bundle cannot be resolved because of
{code}
Caused by: org.apache.felix.log.LogException: org.jboss.osgi.resolver.XResolverException:
Constraint violation for package 'javax.servlet' when resolving module
Module[org.ops4j.pax.web.service:0.5.1] between existing import
Module[org.ops4j.pax.web.service:0.5.1].javax.servlet BLAMED ON
[[Module[org.ops4j.pax.web.service:0.5.1]] package;
(&(package=javax.servlet)(version>=2.3.0)(!(version>=2.6.0)))] and uses
constraint Module[javax.servlet.api:0.0.0].javax.servlet BLAMED ON
[[Module[org.ops4j.pax.web.service:0.5.1]] package;
(&(package=org.osgi.service.http)(version>=1.0.0)(!(version>=2.0.0))),
[Module[osgi.cmpn:4.2.0.200908310645]] package; (package=javax.servlet)]
at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:117)
[jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.spi.AbstractResolver.resolve(AbstractResolver.java:148)
[jbosgi-resolver-spi-1.0.10.jar:1.0.10]
at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:155)
[jbosgi-framework-core-1.0.0.jar:1.0.0]
{code}
That the the bundle is still marked as successfully deployed is ok. It indicates that the
bundle could get installed. See our old friend AS7-378
was (Author: thomas.diesler):
The bundle cannot be resolved because of
{code}
Caused by: org.apache.felix.log.LogException: org.jboss.osgi.resolver.XResolverException:
Constraint violation for package 'javax.servlet' when resolving module
Module[org.ops4j.pax.web.service:0.5.1] between existing import
Module[org.ops4j.pax.web.service:0.5.1].javax.servlet BLAMED ON
[[Module[org.ops4j.pax.web.service:0.5.1]] package;
(&(package=javax.servlet)(version>=2.3.0)(!(version>=2.6.0)))] and uses
constraint Module[javax.servlet.api:0.0.0].javax.servlet BLAMED ON
[[Module[org.ops4j.pax.web.service:0.5.1]] package;
(&(package=org.osgi.service.http)(version>=1.0.0)(!(version>=2.0.0))),
[Module[osgi.cmpn:4.2.0.200908310645]] package; (package=javax.servlet)]
at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:117)
[jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.spi.AbstractResolver.resolve(AbstractResolver.java:148)
[jbosgi-resolver-spi-1.0.10.jar:1.0.10]
at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:155)
[jbosgi-framework-core-1.0.0.jar:1.0.0]
{code}
That the the bundle is still marked as successfully deployed is ok. It indicates that the
bundle could get installed. It is our old friend AS7-378
NPE from the resolver when deploying bundle
-------------------------------------------
Key: AS7-2214
URL:
https://issues.jboss.org/browse/AS7-2214
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Reporter: David Bosschaert
Assignee: Thomas Diesler
Fix For: 7.1.0.Beta1
Attachments: pax-web-service-0.5.1.jar
While I was in the process of getting the CXF DOSGi project to work on AS7 I found that
the resolver was throwing a NPE when a number of bundles were being deployed. It happened
for pax-web-service, cxf-bundle-minimal and cxf-dosgi-dsw.
The simplest way to reproduce it is to take the pax-web-service-0.5.1 bundle. Deploying
that will cause the following exception:
{code}11:23:01,920 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service
thread 1-8) Install bundle: org.ops4j.pax.web.service:0.5.1
11:23:01,942 ERROR [org.jboss.msc.service] (MSC service thread 1-8) MSC00002: Invocation
of listener "org.jboss.as.osgi.deployment.BundleStartTracker$1@7fad5275" failed:
java.lang.NullPointerException
at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:117)
[jbosgi-resolver-felix-1.0.9.jar:1.0.9]
at org.jboss.osgi.resolver.spi.AbstractResolver.resolve(AbstractResolver.java:148)
[jbosgi-resolver-spi-1.0.9.jar:1.0.9]
at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:155)
[jbosgi-framework-core-1.0.0.jar:1.0.0]
at
org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551)
[jbosgi-framework-core-1.0.0.jar:1.0.0]
at
org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:211)
[jbosgi-framework-core-1.0.0.jar:1.0.0]
at
org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494)
[jbosgi-framework-core-1.0.0.jar:1.0.0]
at
org.jboss.as.osgi.deployment.BundleStartTracker$1.processService(BundleStartTracker.java:144)
[jboss-as-osgi-service-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at
org.jboss.as.osgi.deployment.BundleStartTracker$1.transition(BundleStartTracker.java:119)
[jboss-as-osgi-service-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at
org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1429)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
org.jboss.msc.service.ServiceControllerImpl.access$2600(ServiceControllerImpl.java:49)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1952)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
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]
11:23:01,959 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2)
Deployed "pax-web-service-0.5.1.jar"{code}
Also note that the bundle is still marked as successfully deployed, which is probably not
correct.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira