org.apache.felix.log.LogException

org.osgi.framework.BundleException: Cannot resolve bundle resModule: [jbosgi-blueprint:1.0.2]

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web5

  • via Unknown by Unknown author,
  • Stack trace

    • org.apache.felix.log.LogException: org.osgi.framework.BundleException: Cannot resolve bundle resModule: [jbosgi-blueprint:1.0.2] 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:488) at org.jboss.as.osgi.parser.BundleRuntimeHandler.handleOperation(BundleRuntimeHandler.java:132) at org.jboss.as.osgi.parser.BundleRuntimeHandler.executeRuntimeStep(BundleRuntimeHandler.java:89) at org.jboss.as.controller.AbstractRuntimeOnlyHandler$1.execute(AbstractRuntimeOnlyHandler.java:90) at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) at org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:466) at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:121) at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:309) at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:299) at org.jboss.as.domain.http.server.DomainApiHandler.processRequest(DomainApiHandler.java:294) at org.jboss.as.domain.http.server.DomainApiHandler.doHandle(DomainApiHandler.java:201) at org.jboss.as.domain.http.server.DomainApiHandler.handle(DomainApiHandler.java:208) 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:54) 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:1110)[rt.jar:1.7.0_09] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)[rt.jar:1.7.0_09] at java.lang.Thread.run(Thread.java:722)[rt.jar:1.7.0_09] at org.jboss.threads.JBossThread.run(JBossThread.java:122) Caused by: org.apache.felix.log.LogException: org.jboss.osgi.resolver.XResolverException: Unable to resolve Module[jbosgi-blueprint:1.0.2]: missing requirement [Module[jbosgi-blueprint:1.0.2]] package; (&(package=org.jboss.osgi.spi.capability)(version>=1.0.0)(!(version>=2.0.0))) at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:117) at org.jboss.osgi.resolver.spi.AbstractResolver.resolve(AbstractResolver.java:149) at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:155) ... 32 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    We couldn't find other users who have seen this exception.