Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-1561

NullPointerException when deploying WAR on z/OS

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 8.0.0.CR1
    • None
    • None
    • None

    Description

      I am getting a NullPointerException when attempting to deploy a WAR file on a JBoss 7.1.1.Final instance running on an IBM z/OS 1.13 mainframe. I tried running JBoss with IBM Java 6 and 7, both 64-bit, and got the same effect. I should also note that this WAR file contains no JBoss-specific configuration files (it's being ported from another servlet container), and that I do NOT encounter this exception when deploying on the same JBoss release on a Windows 7 machine. I do not know of a workaround for this problem.

      This stack trace appears after the "Starting deployment of app.war" message:

      08:42:33,875 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.unit."app.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."app.war".PARSE: Failed to process phase PARSE of deployment "app.war"
      at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
      at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
      at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0]
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0]
      at java.lang.Thread.run(Thread.java:736) [vm.jar:1.6.0]
      Caused by: java.lang.NullPointerException
      at org.jboss.metadata.parser.util.MetaDataElementParser.readDTDLocation(MetaDataElementParser.java:319)
      at org.jboss.metadata.parser.jsp.TldMetaDataParser.parse(TldMetaDataParser.java:58)
      at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.parseTLD(TldParsingDeploymentProcessor.java:126)
      at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processTlds(TldParsingDeploymentProcessor.java:107)
      at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.deploy(TldParsingDeploymentProcessor.java:83)
      at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
      ... 5 more

      I believe that I tracked down the offending code in the git repository (looks like "loc" is null): https://github.com/jboss/metadata/blob/d3a85c7869430831577035aad153c43203882bb9/common/src/main/java/org/jboss/metadata/parser/util/MetaDataElementParser.java#L319

      Is there any way to enable some sort of logging so that I could see what file JBoss is trying to parse?

      Attachments

        Activity

          People

            rhn-engineering-jclere Jean-Frederic Clere
            mbpolan Mike Polan (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: