4 Replies Latest reply on Oct 30, 2013 5:26 AM by sachin.dhingra

    Failed to process phase STRUCTURE of deployment "xalan.jar"

    sachin.dhingra

      HI,

       

      I am deploying exploded way of ear file which contains jar and war file on JBOSS 7.1.1 final. I have a lib folder inside the exploded folder contains different jar file one of them if xalan.jar but getting below error:

       

      Server.log:

      09:42:52,180 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: Failed to start service jboss.deployment.unit."xalan.jar".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."xalan.jar".STRUCTURE: Failed to process phase STRUCTURE of deployment "xalan.jar"

          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_26]

          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26]

          at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]

      Caused by: java.lang.IllegalArgumentException: Given parent is not an ancestor of this virtual file

          at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:116) [jboss-vfs-3.1.0.Final.jar:3.1.0.Final]

          at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122) [jboss-vfs-3.1.0.Final.jar:3.1.0.Final]

          at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122) [jboss-vfs-3.1.0.Final.jar:3.1.0.Final]

          at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122) [jboss-vfs-3.1.0.Final.jar:3.1.0.Final]

          at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122) [jboss-vfs-3.1.0.Final.jar:3.1.0.Final]

          at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122) [jboss-vfs-3.1.0.Final.jar:3.1.0.Final]

          at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122) [jboss-vfs-3.1.0.Final.jar:3.1.0.Final]

          at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:110) [jboss-vfs-3.1.0.Final.jar:3.1.0.Final]

          at org.jboss.as.server.deployment.module.ManifestClassPathProcessor.createAdditionalModule(ManifestClassPathProcessor.java:193) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]

          at org.jboss.as.server.deployment.module.ManifestClassPathProcessor.handlingExistingClassPathEntry(ManifestClassPathProcessor.java:185) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]

          at org.jboss.as.server.deployment.module.ManifestClassPathProcessor.deploy(ManifestClassPathProcessor.java:160) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]

          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 have extracted the xalan.jar file in a separate folder and seen its MANIFEST.MF file which has below contents:

      Manifest-Version: 1.0

      Created-By: 1.3.1 (IBM Corporation)

      Main-Class: org.apache.xalan.xslt.Process

      Class-Path: xercesImpl.jar xml-apis.jar serializer.jar

       

      Its classpath is referring to three other jar file which are also present in the same lib folder and for them i am getting below warning:

      09:42:51,776 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-8) Class Path entry xml-apis.jar in "/D:/Official/JBoss/jboss-as-7.1.1.Final/bin/content/serializer.jar"  does not point to a valid jar for a Class-Path reference.

       

      And one more thing is for all other addtional jar files inside the lib directory, i am getting below similar error

      09:42:55,934 ERROR [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015892: Deployment unit processor org.jboss.as.jpa.processor.PersistenceProviderProcessor@ed92dbb unexpectedly threw an exception during undeploy phase INSTALL of deployment "jcr-2.0.jar": java.lang.NullPointerException

          at org.jboss.as.jpa.processor.PersistenceProviderProcessor.allDeploymentModuleClassLoaders(PersistenceProviderProcessor.java:138)

          at org.jboss.as.jpa.processor.PersistenceProviderProcessor.undeploy(PersistenceProviderProcessor.java:122)

          at org.jboss.as.server.deployment.DeploymentUnitPhaseService.safeUndeploy(DeploymentUnitPhaseService.java:167) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]

          at org.jboss.as.server.deployment.DeploymentUnitPhaseService.stop(DeploymentUnitPhaseService.java:161) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]

          at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1911) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

          at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1874) [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_26]

          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26]

          at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]

       

      Please help.

        • 1. Re: Failed to process phase STRUCTURE of deployment "xalan.jar"
          ctomc

          Upgrade to any newer version. 7.1.2, 7.1.3 ( you need to build it yourself) or take 7.2.0 (binary build as EAP 6.1.Alpha)

          • 2. Re: Failed to process phase STRUCTURE of deployment "xalan.jar"
            sachin.dhingra

            Hi Tomaz,

             

            Thanks for the response. I am a newbie to JBOSS so could you elaborate why do i need to upgrade my AS?

             

            Also, I tried using the "JBoss Enterprise Application Platform - Version 6.1.0.GA" based upon this link http://www.openlogic.com/blog/bid/283299/Where-is-JBoss-7-2-0-Final.

             

            Now i am not getting the (Failed to process phase STRUCTURE of deployment "xalan.jar" and above mentioned NullPointerException) error but still for all the jars in my lib directory i am getting below warning.

            09:09:16,393 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry xercesImpl.jar in /D:/Official/JBoss/jboss-eap-6.1.0/bin/content/xalan.jar  does not point to a valid jar for a Class-Path reference.

            09:09:16,418 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry xml-apis.jar in /D:/Official/JBoss/jboss-eap-6.1.0/bin/content/xalan.jar  does not point to a valid jar for a Class-Path reference.

            09:09:16,420 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry serializer.jar in /D:/Official/JBoss/jboss-eap-6.1.0/bin/content/xalan.jar  does not point to a valid jar for a Class-Path reference.

             

            Could you provide me what is happening here and how to resolve this?

            • 3. Re: Failed to process phase STRUCTURE of deployment "xalan.jar"
              jaikiran

              Sachin Dhingra wrote:

               

              Hi Tomaz,

               

              Thanks for the response. I am a newbie to JBOSS so could you elaborate why do i need to upgrade my AS?

               

              JBoss AS 7.1.1 was released more than 1.5 years ago. Numerous bugs have been fixed and there have been releases after that. So in general, we ask users to test this against latest versions to verify if the issue has been fixed in a later version.

              • 4. Re: Failed to process phase STRUCTURE of deployment "xalan.jar"
                sachin.dhingra

                That is fine Jaikiran but even after using the JBoss EAP 6.1.0 which I found latest JBoss version. For that only the above warning is coming.