[JBoss JIRA] (AS7-2394) Deployment of a bundle that imports javax.servlet [2.3, 2.6) fails while the bundle itself exports javax.servlet 2.5
by David Bosschaert (Created) (JIRA)
Deployment of a bundle that imports javax.servlet [2.3,2.6) fails while the bundle itself exports javax.servlet 2.5
-------------------------------------------------------------------------------------------------------------------
Key: AS7-2394
URL: https://issues.jboss.org/browse/AS7-2394
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: 7.1.0.Beta1
Reporter: David Bosschaert
Assignee: Thomas Diesler
Deploy the pax-web-service ( https://issues.jboss.org/secure/attachment/12348289/pax-web-service-0.5.1... ) into a default build of AS7 and you get the following exception:
{code}14:08:30,891 DEBUG [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Deployment scan of [/Users/david/clones/bosschaert_jboss-as_171011/build/target/jboss-as-7.1.0.Alpha2-SNAPSHOT/standalone/deployments] found update action [{
"operation" => "composite",
"address" => undefined,
"steps" => [
{
"operation" => "add",
"address" => [("deployment" => "pax-web-service-0.5.1.jar")],
"content" => [{
"path" => "deployments/pax-web-service-0.5.1.jar",
"relative-to" => "jboss.server.base.dir",
"archive" => true
}],
"persistent" => false
},
{
"operation" => "deploy",
"address" => [("deployment" => "pax-web-service-0.5.1.jar")]
}
]
}]
14:08:30,900 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) Starting deployment of "pax-web-service-0.5.1.jar"
14:08:31,000 DEBUG [org.jboss.as.server.deployment.module] (MSC service thread 1-2) Found Extension-Name manifest entry null in /content/pax-web-service-0.5.1.jar
14:08:31,015 DEBUG [org.jboss.as.jpa] (MSC service thread 1-6) added javax.persistence.api dependency to pax-web-service-0.5.1.jar
14:08:31,035 DEBUG [org.jboss.as.osgi] (MSC service thread 1-13) Starting: service jboss.osgi.deployment."pax-web-service-0.5.1.jar" in mode ACTIVE
14:08:31,044 DEBUG [org.jboss.osgi.framework.internal.AbstractBundleService] (MSC service thread 1-8) Starting: service jbosgi.bundle.23."org.ops4j.pax.web.service"."0.5.1".INSTALLED in mode ACTIVE
14:08:31,047 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-8) Install bundle: org.ops4j.pax.web.service:0.5.1
14:08:31,057 DEBUG [org.jboss.osgi.resolver.felix.LoggerDelegate] (MSC service thread 1-16) Conflict between imports: org.apache.felix.framework.resolver.ResolveException: 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.ops4j.pax.web.service)(version>=0.5.1)), [Module[jbosgi-http:1.0.5]] package; (&(package=javax.servlet)(version>=2.5.0)(!(version>=4.0.0)))]
at org.apache.felix.framework.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1013) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.apache.felix.framework.resolver.ResolverImpl.resolve(ResolverImpl.java:106) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.felix.ResolverExt.resolve(ResolverExt.java:48) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:140) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:110) [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.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:211) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494) [jbosgi-framework-core-1.0.1.jar:1.0.1]
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]
14:08:31,059 DEBUG [org.jboss.osgi.resolver.felix.LoggerDelegate] (MSC service thread 1-16) [org.ops4j.pax.web.service:0.5.1] Current candidate permutation failed, will try another if possible.: org.apache.felix.framework.resolver.ResolveException: 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.ops4j.pax.web.service)(version>=0.5.1)), [Module[jbosgi-http:1.0.5]] package; (&(package=javax.servlet)(version>=2.5.0)(!(version>=4.0.0)))]
at org.apache.felix.framework.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1013) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.apache.felix.framework.resolver.ResolverImpl.resolve(ResolverImpl.java:106) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.felix.ResolverExt.resolve(ResolverExt.java:48) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:140) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:110) [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.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:211) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494) [jbosgi-framework-core-1.0.1.jar:1.0.1]
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]
14:08:31,064 DEBUG [org.jboss.osgi.resolver.felix.LoggerDelegate] (MSC service thread 1-16) Conflict between imports: org.apache.felix.framework.resolver.ResolveException: 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.apache.felix.framework.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1013) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.apache.felix.framework.resolver.ResolverImpl.resolve(ResolverImpl.java:106) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.felix.ResolverExt.resolve(ResolverExt.java:48) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:140) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:110) [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.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:211) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494) [jbosgi-framework-core-1.0.1.jar:1.0.1]
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]
14:08:31,065 DEBUG [org.jboss.osgi.resolver.felix.LoggerDelegate] (MSC service thread 1-16) [org.ops4j.pax.web.service:0.5.1] Current candidate permutation failed, will try another if possible.: org.apache.felix.framework.resolver.ResolveException: 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.apache.felix.framework.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1013) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.apache.felix.framework.resolver.ResolverImpl.resolve(ResolverImpl.java:106) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.felix.ResolverExt.resolve(ResolverExt.java:48) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:140) [jbosgi-resolver-felix-1.0.10.jar:1.0.10]
at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:110) [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.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:211) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494) [jbosgi-framework-core-1.0.1.jar:1.0.1]
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]
14:08:31,067 ERROR [org.jboss.osgi.framework.internal.FrameworkEventsPlugin] (MSC service thread 1-16) Framework ERROR: org.osgi.framework.BundleException: Cannot resolve bundle resModule: [org.ops4j.pax.web.service:0.5.1]
at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:157) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:211) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494) [jbosgi-framework-core-1.0.1.jar:1.0.1]
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]
Caused by: 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.1.jar:1.0.1]
... 11 more
14:08:31,068 ERROR [org.jboss.as.osgi] (MSC service thread 1-16) JBAS011912: Cannot start bundle: org.ops4j.pax.web.service:0.5.1: org.osgi.framework.BundleException: Cannot resolve bundle: org.ops4j.pax.web.service:0.5.1
at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:212) [jbosgi-framework-core-1.0.1.jar:1.0.1]
at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494) [jbosgi-framework-core-1.0.1.jar:1.0.1]
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]
14:08:31,068 ERROR [org.ops4j.pax.web.service] (Thread-27) FrameworkEvent ERROR: org.apache.felix.log.LogException: org.osgi.framework.BundleException: Cannot resolve bundle resModule: [org.ops4j.pax.web.service:0.5.1]
at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:157)
at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551)
at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:211)
at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494)
at org.jboss.as.osgi.deployment.BundleStartTracker$1.processService(BundleStartTracker.java:144)
at org.jboss.as.osgi.deployment.BundleStartTracker$1.transition(BundleStartTracker.java:119)
at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1429)
at org.jboss.msc.service.ServiceControllerImpl.access$2600(ServiceControllerImpl.java:49)
at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1952)
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]
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)
at org.jboss.osgi.resolver.spi.AbstractResolver.resolve(AbstractResolver.java:148)
at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:155)
... 11 more
{code}
--
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
14 years, 8 months
[JBoss JIRA] (JBRULES-3271) Make rule context available to enumeration loaders
by G Patel (Created) (JIRA)
Make rule context available to enumeration loaders
--------------------------------------------------
Key: JBRULES-3271
URL: https://issues.jboss.org/browse/JBRULES-3271
Project: Drools
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Reporter: G Patel
Assignee: Mark Proctor
Currently, only fact field names are passed into data enumeration loaders. Sometimes, the enumeration list might need to change based on details about the rule being edited, like rule metadata or package name, etc. The request is to make the Rule object (along with all of it's metadata) available to data enumeration loaders. Perhaps have loaders implement the following interface:
public interface EnumLoader{
public List<String> loadEnum(Rule r, String... dependentFields);
}
This will enable support for more contextual enum lists. Very helpful for folks trying to integrate the standalone rule editor into applications.
--
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
14 years, 8 months
[JBoss JIRA] (AS7-2426) If a slave host controller fails authentication it just keeps re-trying
by Darran Lofthouse (Created) (JIRA)
If a slave host controller fails authentication it just keeps re-trying
-----------------------------------------------------------------------
Key: AS7-2426
URL: https://issues.jboss.org/browse/AS7-2426
Project: Application Server 7
Issue Type: Bug
Components: Domain Management, Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 7.1.0.CR1
If the slave host controller can not connect to the master host controller due to failed authentication the following message is continually logged as it keeps retrying.
"JBREM000200: Remote connection failed: javax.security.sasl.SaslException: No more authentication mechanisms to try"
In general for clients connecting using Remoting and authenticating we probably want something more specific to indicate a failed authentication as retrying is probably never going to work.
The looping here is also bad if a form of brute force defense is added as this may appear as an attack.
--
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
14 years, 9 months
[JBoss JIRA] (JBJCA-694) SonicMQ RA in JBoss7 showing lots of IJ000612 warnings (Destroying connection that could not be successfully matched)
by Robert Stupp (Created) (JIRA)
SonicMQ RA in JBoss7 showing lots of IJ000612 warnings (Destroying connection that could not be successfully matched)
---------------------------------------------------------------------------------------------------------------------
Key: JBJCA-694
URL: https://issues.jboss.org/browse/JBJCA-694
Project: IronJacamar
Issue Type: Bug
Affects Versions: 1.0.5.Final
Environment: Linux *2.6.32-71.29.1.el6.x86_64 #1 SMP x86_64 x86_64 x86_64 GNU/Linux
java version "1.6.0_27"
Java(TM) SE Runtime Environment (build 1.6.0_27-b07)
Java HotSpot(TM) 64-Bit Server VM (build 20.2-b06, mixed mode)
JBoss 7.1.0.Alpha2 AS with current code from git
Reporter: Robert Stupp
Assignee: Jesper Pedersen
Basic integration of SonicMQ RA (version 8.5) works.
But when using JMeter with many parallel requests provoke a lot of these warnings:
{noformat}
17:25:38,489 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (http--0.0.0.0-8080-5) IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@7df5f91c[state=NORMAL managed connection=com.sonicsw.sonicmq.j2ee.jmsra.impl.JMSSessionManagedConnection@24f1c9c6 connection handles=0 lastUse=1319815538489 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@6dbd726 pool internal context=org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool@2fb8c90 xaResource=XAResourceWrapperImpl@1fb5dddf[xaResource=com.sonicsw.sonicmq.j2ee.jmsra.impl.XAResourceWrapper(a)5cf96bbc pad=false overrideRmValue=false productName=java:/XAConnectionFactory productVersion=java:/XAConnectionFactory jndiName=java:/XAConnectionFactory] txSync=null]
{noformat}
With tracing enabled, JCA core connection manager tells this (before the message above):
{noformat}
17:25:38,487 TRACE [org.jboss.jca.core.connectionmanager.listener.TxConnectionListener] (http--0.0.0.0-8080-10) connectionClosed called mc=com.sonicsw.sonicmq.j2ee.jmsra.impl.JMSSessionManagedConnection@24f1c9c6
17:25:38,487 TRACE [org.jboss.jca.core.connectionmanager.listener.TxConnectionListener] (http--0.0.0.0-8080-10) unregisterConnection: 0 handles left
17:25:38,487 TRACE [org.jboss.jca.core.connectionmanager.listener.TxConnectionListener] (http--0.0.0.0-8080-10) delisting org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@7df5f91c[state=NORMAL managed connection=com.sonicsw.sonicmq.j2ee.jmsra.impl.JMSSessionManagedConnection@24f1c9c6 connection handles=0 lastUse=1319815538458 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@6dbd726 pool internal context=org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool@2fb8c90 xaResource=XAResourceWrapperImpl@1fb5dddf[xaResource=com.sonicsw.sonicmq.j2ee.jmsra.impl.XAResourceWrapper(a)5cf96bbc pad=false overrideRmValue=false productName=java:/XAConnectionFactory productVersion=java:/XAConnectionFactory jndiName=java:/XAConnectionFactory] txSync=null]
17:25:38,487 TRACE [org.jboss.jca.core.connectionmanager.listener.TxConnectionListener] (http--0.0.0.0-8080-10) isManagedConnectionFree=true mc=com.sonicsw.sonicmq.j2ee.jmsra.impl.JMSSessionManagedConnection@24f1c9c6
17:25:38,489 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (http--0.0.0.0-8080-5) IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@7df5f91c[state=NORMAL managed connection=com.sonicsw.sonicmq.j2ee.jmsra.impl.JMSSessionManagedConnection@24f1c9c6 connection handles=0 lastUse=1319815538489 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@6dbd726 pool internal context=org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool@2fb8c90 xaResource=XAResourceWrapperImpl@1fb5dddf[xaResource=com.sonicsw.sonicmq.j2ee.jmsra.impl.XAResourceWrapper(a)5cf96bbc pad=false overrideRmValue=false productName=java:/XAConnectionFactory productVersion=java:/XAConnectionFactory jndiName=java:/XAConnectionFactory] txSync=null]
... (somthing else happens in other threads) ...
17:25:38,489 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (http--0.0.0.0-8080-5) IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@7df5f91c[state=NORMAL managed connection=com.sonicsw.sonicmq.j2ee.jmsra.impl.JMSSessionManagedConnection@24f1c9c6 connection handles=0 lastUse=1319815538489 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@6dbd726 pool internal context=org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool@2fb8c90 xaResource=XAResourceWrapperImpl@1fb5dddf[xaResource=com.sonicsw.sonicmq.j2ee.jmsra.impl.XAResourceWrapper(a)5cf96bbc pad=false overrideRmValue=false productName=java:/XAConnectionFactory productVersion=java:/XAConnectionFactory jndiName=java:/XAConnectionFactory] txSync=null]
{noformat}
-----------------------------------------
Related to the above (but slightly different messages (productName, productVersion):
The first request (after JBoss 7 startup) issues exactly as many of these warnings as the configured minimum pool size. For example: min-size=20 forces 20 of the following messages:
{noformat}
17:18:21,545 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (http--0.0.0.0-8080-1) IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@7d3e3b95[state=NORMAL managed connection=com.sonicsw.sonicmq.j2ee.jmsra.impl.JMSSessionManagedConnection@b9f370 connection handles=0 lastUse=1319815093744 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@6dbd726 pool internal context=org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool@2fb8c90 xaResource=XAResourceWrapperImpl@301d3e6f[xaResource=com.sonicsw.sonicmq.j2ee.jmsra.impl.XAResourceWrapper(a)4fee0216 pad=false overrideRmValue=false productName=SonicMQ productVersion=8.5.377 jndiName=java:/XAConnectionFactory] txSync=null]
17:18:21,547 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (http--0.0.0.0-8080-1) IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@12cb1b59[state=NORMAL managed connection=com.sonicsw.sonicmq.j2ee.jmsra.impl.JMSSessionManagedConnection@547079b2 connection handles=0 lastUse=1319815093742 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@6dbd726 pool internal context=org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool@2fb8c90 xaResource=XAResourceWrapperImpl@2445c06d[xaResource=com.sonicsw.sonicmq.j2ee.jmsra.impl.XAResourceWrapper(a)5f5c46b5 pad=false overrideRmValue=false productName=SonicMQ productVersion=8.5.377 jndiName=java:/XAConnectionFactory] txSync=null]
17:18:21,550 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (http--0.0.0.0-8080-1) IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@232645fc[state=NORMAL managed connection=com.sonicsw.sonicmq.j2ee.jmsra.impl.JMSSessionManagedConnection@25bcb56b connection handles=0 lastUse=1319815093740 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@6dbd726 pool internal context=org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool@2fb8c90 xaResource=XAResourceWrapperImpl@82a9728[xaResource=com.sonicsw.sonicmq.j2ee.jmsra.impl.XAResourceWrapper(a)2429c748 pad=false overrideRmValue=false productName=SonicMQ productVersion=8.5.377 jndiName=java:/XAConnectionFactory] txSync=null]
... (17 more)
{noformat}
I am not sure whether this is caused by ironjacamar or JBoss7 code.
--
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
14 years, 9 months
[JBoss JIRA] Created: (AS7-851) Add some form of :whoami operation
by Darran Lofthouse (JIRA)
Add some form of :whoami operation
----------------------------------
Key: AS7-851
URL: https://issues.jboss.org/browse/AS7-851
Project: Application Server 7
Issue Type: Task
Components: Domain Management
Reporter: Darran Lofthouse
Assignee: Jason Greene
Fix For: 7.0.0.CR1
Connectivity to the server can make use of authentication automatically handled by either the web broswer or in some cases possibly a CLI using a local Kerberos ticket.
This issue is to add a :whoami operation to verify who the connection is running as so the client can see they are connected as the expected user.
Later this may also be expanded to make it possible to query what a client can actually do so operations a client can not perform can be potentially hidden / masked.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months