11 Replies Latest reply on Nov 30, 2010 9:03 PM by Brian Stansberry

    NPE in StandaloneClientImpl.isDeploymentNameUnique

    Thomas Diesler Master
      Caused by: org.jboss.as.protocol.mgmt.ManagementException: Failed to check deployment name uniqueness.
           at org.jboss.as.standalone.client.impl.StandaloneClientImpl.isDeploymentNameUnique(StandaloneClientImpl.java:130)
           at org.jboss.as.standalone.client.impl.StandaloneClientDeploymentManager$1.distributeDeploymentContent(StandaloneClientDeploymentManager.java:59)
           at org.jboss.as.standalone.client.impl.deployment.DeploymentPlanBuilderImpl.add(DeploymentPlanBuilderImpl.java:187)
           at org.jboss.as.standalone.client.impl.deployment.DeploymentPlanBuilderImpl.add(DeploymentPlanBuilderImpl.java:182)
           at org.jboss.osgi.plugin.jbossas7.DeployerClientImpl.deploy(DeployerClientImpl.java:85)
           ... 31 more
      Caused by: java.lang.NullPointerException
           at org.jboss.as.standalone.client.impl.StandaloneClientImpl.isDeploymentNameUnique(StandaloneClientImpl.java:128)
           ... 35 more
      

       

      This repeatedly happens on the EC2 Hudson instance, but cannot be reproduces locally.

       

          boolean isDeploymentNameUnique(String name) {
              try {
          128:     return new CheckUnitDeploymentNameOperation(name).executeForResult(getConnectionStrategy());
              } catch (Exception e) {
                  throw new ManagementException("Failed to check deployment name uniqueness.", e);
              }
          }
       
      
      
      

       

      Any idea, how a NPE is even possible given the trace above.