Major 11:42:46,873 INFO [org.jboss.as.osgi] (HttpManagementService-threads - 2) JBAS011916: Activate deferred module phase for: org.springframework.jms:3.2.2.RELEASE 11:42:46,874 ERROR [org.jboss.as.osgi] (HttpManagementService-threads - 2) JBAS011909: Management operation 'start' failed: org.osgi.framework.BundleException: JBOSGI011250: Cannot resolve bundle: org.springframework.jms:3.2.2.RELEASE at org.jboss.as.osgi.service.BundleLifecycleIntegration$BundleLifecycleImpl.activateDeferredPhase(BundleLifecycleIntegration.java:299) at org.jboss.as.osgi.service.BundleLifecycleIntegration$BundleLifecycleImpl.start(BundleLifecycleIntegration.java:229) at org.jboss.osgi.framework.internal.AbstractBundleState.startWithOptions(AbstractBundleState.java:537) at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:525) at org.jboss.as.osgi.management.BundleResourceHandler.handleOperation(BundleResourceHandler.java:106) at org.jboss.as.osgi.management.BundleResourceHandler.executeRuntimeStep(BundleResourceHandler.java:58) at org.jboss.as.controller.AbstractRuntimeOnlyHandler$1.execute(AbstractRuntimeOnlyHandler.java:90) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:142) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:112) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] at org.jboss.as.controller.ModelControllerImpl$2.execute(ModelControllerImpl.java:338) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] at org.jboss.as.controller.ModelControllerImpl$2.execute(ModelControllerImpl.java:328) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] at org.jboss.as.domain.http.server.DomainApiHandler.processRequest(DomainApiHandler.java:320) at org.jboss.as.domain.http.server.DomainApiHandler.doHandle(DomainApiHandler.java:226) at org.jboss.as.domain.http.server.DomainApiHandler.handle(DomainApiHandler.java:233) at org.jboss.as.domain.http.server.security.SubjectAssociationHandler.handle(SubjectAssociationHandler.java:51) at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78) at org.jboss.sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:69) at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81) at org.jboss.sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:710) at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78) at org.jboss.as.domain.http.server.RealmReadinessFilter.doFilter(RealmReadinessFilter.java:47) at org.jboss.as.domain.http.server.DmrFailureReadinessFilter.doFilter(DmrFailureReadinessFilter.java:45) at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81) at org.jboss.sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:682) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13] at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final.jar:2.1.0.Final] Caused by: org.osgi.service.resolver.ResolutionException: Unable to resolve HostBundleRevision[org.springframework.jms:3.2.2.RELEASE]: missing requirement XPackageRequirement[atts={osgi.wiring.package=javax.jms, version=[1.1.0, 2.0.0)},[org.springframework.jms:3.2.2.RELEASE]] at org.apache.felix.resolver.Candidates.populateResource(Candidates.java:285) at org.apache.felix.resolver.Candidates.populate(Candidates.java:153) at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:96) at org.jboss.osgi.resolver.felix.StatelessResolver.resolve(StatelessResolver.java:56) at org.jboss.osgi.framework.internal.ResolverImpl.resolveAndApply(ResolverImpl.java:137) at org.jboss.as.osgi.service.BundleLifecycleIntegration$BundleLifecycleImpl.activateDeferredPhase(BundleLifecycleIntegration.java:296) ... 31 more
- relates to
-
AS7-2959 Adding <capability name="javax.jms.api"/> to standalone.xml's osgi section does not result in the javax.jms api's being visible to OSGi bundles.
-
- Resolved
-
[AS7-6883] javax.jms package is not exported when running with standalone-osgi.xml
Please show us the configuration and the section of the debug log that shows set set of resource caps/reqs
It should look similar to
11:05:15,797 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-5) Install resource: AbstractBundleRevisionAdaptor[org.jboss.spec.javax.jms.jboss-jms-api_1.1_spec:1.0.1.Final]
11:05:15,797 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-5) XIdentityCapability[atts={osgi.identity=org.jboss.spec.javax.jms.jboss-jms-api_1.1_spec, version=1.0.1.Final, type=osgi.bundle},[org.jboss.spec.javax.jms.jboss-jms-api_1.1_spec:1.0.1.Final]]
11:05:15,797 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-5) XResourceCapability[atts={osgi.wiring.bundle=org.jboss.spec.javax.jms.jboss-jms-api_1.1_spec, bundle-version=1.0.1.Final},[org.jboss.spec.javax.jms.jboss-jms-api_1.1_spec:1.0.1.Final]]
11:05:15,798 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-5) XHostCapability[atts={osgi.wiring.host=org.jboss.spec.javax.jms.jboss-jms-api_1.1_spec, bundle-version=1.0.1.Final},[org.jboss.spec.javax.jms.jboss-jms-api_1.1_spec:1.0.1.Final]]
11:05:15,798 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-5) XPackageCapability[atts={osgi.wiring.package=javax.jms, version=1.1.0, bundle-symbolic-name=org.jboss.spec.javax.jms.jboss-jms-api_1.1_spec, bundle-version=1.0.1.Final, specification-version=1.1.0},dirs={uses=javax.transaction.xa},[org.jboss.spec.javax.jms.jboss-jms-api_1.1_spec:1.0.1.Final]]
11:05:15,798 DEBUG [org.jboss.osgi.resolver] (MSC service thread 1-5) XPackageRequirement[dirs={filter=(osgi.wiring.package=javax.transaction.xa)},[org.jboss.spec.javax.jms.jboss-jms-api_1.1_spec:1.0.1.Final]]
Jeff Mesnil
added a comment - the JMS jar looks to provide the correct OSGi header. You may have a better idea on why this does not work with org.springframework.jms
Jeff Mesnil
added a comment - the JMS jar looks to provide the correct OSGi header. You may have a better idea on why this does not work with org.springframework.jms Jeff Mesnil
added a comment - The jboss-jms-api_1.1_spec-1.0.1.Final.jar file looks to provide the correct OSGi header:
Bundle-Name: Java(TM) Message Service (JMS) 1.1 API Bundle-SymbolicName: org.jboss.spec.javax.jms.jboss-jms-api_1.1_spec Bundle-Vendor: JBoss by Red Hat Bundle-Version: 1.0.1.Final Export-Package: javax.jms;uses:="javax.transaction.xa";version="1.1" Import-Package: javax.transaction.xa
tdiesler@redhat.com I assign the issue to you as I don't think there is anything wrong in the JMS jar with regards to OSGi. It's looks like a pb with OSGi (or org.springframework.jms)
Jeff Mesnil
added a comment - The jboss-jms-api_1.1_spec-1.0.1.Final.jar file looks to provide the correct OSGi header:
Bundle-Name: Java(TM) Message Service (JMS) 1.1 API
Bundle-SymbolicName: org.jboss.spec.javax.jms.jboss-jms-api_1.1_spec
Bundle-Vendor: JBoss by Red Hat
Bundle-Version: 1.0.1.Final
Export-Package: javax.jms;uses:="javax.transaction.xa";version="1.1"
Import-Package: javax.transaction.xa
tdiesler@redhat.com I assign the issue to you as I don't think there is anything wrong in the JMS jar with regards to OSGi. It's looks like a pb with OSGi (or org.springframework.jms) 
The javax.jms.api module exports that package.