Uploaded image for project: 'Application Server 7'
  1. Application Server 7
  2. AS7-2214

NPE from the resolver when deploying bundle

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.1.0.Beta1
    • None
    • OSGi
    • None

    Description

      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:

      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"

      Also note that the bundle is still marked as successfully deployed, which is probably not correct.

      Attachments

        Activity

          People

            tdiesler@redhat.com Thomas Diesler
            dhildenb@redhat.com David Hildenbrand
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: