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

[jrountree]

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.

[jrountree]

Interesting update. I've tried a great deal of things to work around this issue. I removed all of the files from the ear deployment except for an empty war. This results in the same error as above. This means that the problem lies directly in my modules directory. I have added a custom login module that must be causing an issue with the jboss-modules.jar. I'm still not entirely sure if this module is the culprit, but failing to deploy an empty ear seems to have narrowed my search.

[jaikiran]

That does look like a bug. I think you should create a WFLY JIRA and attach a simple application that reproduces it.

[ctomc]

any chance you can provide sample ear deployment that can reproduce this?

This way it will be much easier to debug and fix.

[jrountree]

Working on creating a sample ear right now. I'll post it as soon as I have something that is 100 percent reproducible.

[jrountree]

I've found the source of the issue. Oddly enough the issue is being caused by a Hibernate 3.6 jar in the org.hibernate.3 module folder. I added the hibernate3.jar and adjusted the module.xml and then in the standalone*.xml, under domain:ee:2.0, i added

<global-modules>

<module name="org.hibernate" slot="3"/>

</global-modules>

I then attempted to deploy an empty ear with an empty war subdeployment. The same IllegalArgumentException occurred. I could attach the sample ear, but there is literally nothing in it.

I was able to work around this issue by removing the global modules section from the standalone*.xml and adding a dependency in a jboss-deploy-structure.xml. I also disabled jipijapa because it was causing other issues after correcting the IllegalArgumentException. There seems to be some conflicts between Hibernate 3.6 and jipijapa when using JPA with Hibernate.

[virendra656]

Can you please tell me what changes you made into jboss-deployment-structure.xml to solve this error.