2 Replies Latest reply on Jan 21, 2013 12:16 PM by Kermit Tensmeyer

    How do I:  log levels diagnose /=/  Given parent is not an ancestor of this virtual file

    Kermit Tensmeyer Newbie

      When I attempt to load  a 3rd Party war file using the cli    "deploy liferay-portal-6.1.20.war --server-groups=liferay-server-group" It fails.

       

      What I'd like to do is to rerun this set of commands, but increase the levels of logging for the modules.[ What modules, what log4j sections] [is it possible to change at run-time?]

        I would like to identify which of entries in the WAR file generate this type of exception.

      My assumption that a fix/patch for jboss7.1.1 is neither desired or required, but that changes will either be made in the 3rd party module -or- some configuration entry that I've made.

       

         thank you

            Kermit Tensmeyer

       

      ==========================================================================================================================================

      [Server:liferay-one] 11:44:13,936 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.unit."liferay-portal-6.1.20.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."liferay-portal-6.1.20.war".STRUCTURE: Failed to process phase STRUCTURE of deployment "liferay-portal-6.1.20.war"

      [Server:liferay-one]    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]

      [Server:liferay-one]    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

      [Server:liferay-one]    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

      [Server:liferay-one]    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_38]

      [Server:liferay-one]    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_38]

      [Server:liferay-one]    at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_38]

       

      [Server:liferay-one] Caused by: java.lang.IllegalArgumentException: Given parent is not an ancestor of this virtual file

       

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

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

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

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

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

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

      [Server:liferay-one]    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]

      [Server:liferay-one]    ... 5 more

      [Server:liferay-one]

       

      [Server:liferay-one] 11:44:13,952 INFO  [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS015870: Deploy of deployment "liferay-portal-6.1.20.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"liferay-portal-6.1.20.war\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"liferay-portal-6.1.20.war\".STRUCTURE: Failed to process phase STRUCTURE of deployment \"liferay-portal-6.1.20.war\""}}

       

      [Server:liferay-one] 11:44:13,955 INFO  [org.jboss.as.controller] (host-controller-connection-threads - 1) JBAS014774: Service status report

      [Server:liferay-one] JBAS014777:   Services which failed to start:      service jboss.deployment.unit."liferay-portal-6.1.20.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."liferay-portal-6.1.20.war".STRUCTURE: Failed to process phase STRUCTURE of deployment "liferay-portal-6.1.20.war"

      [Server:liferay-one]

      [Server:liferay-one] 11:44:13,964 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment liferay-portal-6.1.20.war in 11ms

        • 1. Re: How do I:  log levels diagnose /=/  Given parent is not an ancestor of this virtual file
          Nicklas Karlsson Master

          Can you deploy it on a standalone server? What's in the manifest of the war itself?

          • 2. Re: How do I:  log levels diagnose /=/  Given parent is not an ancestor of this virtual file
            Kermit Tensmeyer Newbie

            I could do that. 

             

            I could then guess at which element might give me trouble in the domain environment.

             

              Or  I could enable detailed logging for the iterator:  checking the contents of incoming package, and let it tell me which  resource has an issue (inside of a manifest.xml) or inside of a project jar, or a a resource jar or ....

             

            enabling sections of Log4J support areas works if you know what the support sections are.

               I don't know the sections of JBoss 7.x.x yet, I did know the sections for tomcat and WebSphere. In either of those environments, enabling the logging would have generated much more output, but it would also have given me more detail in which to more closely identify the actual cause.

             

              oh by the way,  this application loads just fine under standalone. "Given parent is not an ancestor of this virtual file"   isn't an issue in a standalone environment  (nor was it an issue in JBoss 6 or JBoss 5)

             

            ------

              When I can point to a specfic element inside of the 3rd party war file as causing the problem, it will be much easier to get that 3rd party to fix the problem under a support contract.