6 Replies Latest reply on Mar 27, 2018 8:17 AM by Virendra Rathore

    Wildfly 8.2.0 Final - IllegalArgumentException: Cannot compare relative and absolute paths

    Josh rountree Newbie

      Hey Everyone,


      I've been upgrading my current project from Jboss AS 7.1.1 to Wildfly 8.2.0 and have run into an issue that has stumped me for a couple days now. The error that is blocking me is as follows:


      Caused by: java.lang.IllegalArgumentException: Cannot compare relative and absolute paths

      at org.jboss.modules.PathUtils.isDirectChild(PathUtils.java:243) [jboss-modules.jar:1.3.3.Final]

      at org.jboss.modules.JarFileResourceLoader$1.hasNext(JarFileResourceLoader.java:246) [jboss-modules.jar:1.3.3.Final]

      at org.jboss.modules.ModuleClassLoader$3.hasNext(ModuleClassLoader.java:730) [jboss-modules.jar:1.3.3.Final]

      at org.jboss.modules.Module$3.hasNext(Module.java:735) [jboss-modules.jar:1.3.3.Final]

      at org.jboss.modules.filter.PathFilters$1.hasNext(PathFilters.java:227) [jboss-modules.jar:1.3.3.Final]

      at org.wildfly.extension.undertow.deployment.ExternalTldParsingDeploymentProcessor.deploy(ExternalTldParsingDeploymentProcessor.java:85)

      at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]

      ... 5 more


      This issue occurs when attempting to load the war subdeployment in my ear project. This issue does not occur if the war is moved out of the ear, but this would cause a serious ammount of reworking. I have attempted to deploy with a Jboss-deployment-structure.xml pointing out the subdeployment and get the same issue stated above.

      There is a similar jira issue on the Module Jira which was resolved with Jboss-modules version 1.2.2. That issue can be found here - [MODULES-168] Cannot iterate over module resources on WinOS - JBoss Issue Tracker

      Does anyone have any insight to what I might be doing wrong? Or is this an issue with the modules framework that has been reintroduced? Any insight would be helpful. Server Log has been attached.