Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-3440

On Windows container-create-child root container causes NullPointerException with jboss-fuse-full-6.2.0.redhat-128.zip

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • jboss-fuse-6.2.1
    • jboss-fuse-6.2
    • Fabric8 v1
    • None
    • % %
    • Hide

      See issue description

      Show
      See issue description

    Description

      • When using "jboss-fuse-full-6.2.0.redhat-128.zip" and after starting a fresh fuse instance following the below mentioned steps causes "NullPointerException" 
            fabric:create --wait-for-provisioning
    container-create-child root container
    wait-for-provisioning

        Check the karaf log of the container:

      2015-06-17 17:17:30,322 | WARN  | admin-1-thread-1 | FabricConfigAdminBridge          | 82 - io.fabric8.fabric-configadmin - 1.2.0.redhat-128 | Exception when tracking configurations. This exception will be ignored.
java.lang.NullPointerException
	at io.fabric8.internal.ContainerImpl.getContainerProfile(ContainerImpl.java:764)[79:io.fabric8.fabric-core:1.2.0.redhat-128]
	at io.fabric8.internal.ContainerImpl.getOverlayProfile(ContainerImpl.java:306)[79:io.fabric8.fabric-core:1.2.0.redhat-128]
	at io.fabric8.configadmin.FabricConfigAdminBridge.updateInternal(FabricConfigAdminBridge.java:126)[82:io.fabric8.fabric-configadmin:1.2.0.redhat-128]
	at io.fabric8.configadmin.FabricConfigAdminBridge.access$000(FabricConfigAdminBridge.java:52)[82:io.fabric8.fabric-configadmin:1.2.0.redhat-128]
	at io.fabric8.configadmin.FabricConfigAdminBridge$1.run(FabricConfigAdminBridge.java:106)[82:io.fabric8.fabric-configadmin:1.2.0.redhat-128]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)[:1.7.0_72]
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)[:1.7.0_72]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_72]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_72]
	at java.lang.Thread.run(Thread.java:745)[:1.7.0_72]

      https://repository.jboss.org/nexus/content/groups/ea/org/jboss/fuse/jboss-fuse-full/6.2.0.redhat-128/

      Workaround
      Restart Fabric node instance just after fabric:create

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-3503 "container root does not exist" when creating fabric on Windows

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-3447 missing auth bundle when starting fuse on windows

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-4184 [Patch mechanism 050] Unable to install patch on windows

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-3503 "container root does not exist" when creating fabric on Windows

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              pantinor@redhat.com Paolo Antinori
              jaysensharma Jay SenSharma (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: