[jboss-jira] [JBoss JIRA] (WFLY-9919) Deployment throwing exception on upgrade to JBOSS EAP 7.1

Sainath Machupalli created WFLY-9919: ---------------------------------------- Summary: Deployment throwing exception on upgrade to JBOSS EAP 7.1 Key: WFLY-9919 URL: https://issues.jboss.org/browse/WFLY-9919 Project: WildFly Issue Type: Bug Reporter: Sainath Machupalli Assignee: Jason Greene Priority: Critical Our deployment worked on EAP 7 and we started seeing the below exception when we upgraded to EAP 7.1. 2018-02-07 09:19:46,234 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment inner.war 2018-02-07 09:19:46,239 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.subunit."myEAR.ear"."inner.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."myEAR.ear"."inner.war".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of subdeployment "inner.war" of deployment "myEAR.ear" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.IllegalArgumentException: VFS000025: Given parent ("/content/myEAR.ear/inner.war") is not an ancestor of this virtual file at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:119) at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125) at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125) at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125) at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125) at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:125) at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:112) at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor$ResourceRootHandler.createBeanArchiveId(BeanArchiveProcessor.java:348) at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor$ResourceRootHandler.processResourceRoot(BeanArchiveProcessor.java:296) at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor$ResourceRootHandler.handleResourceRoot(BeanArchiveProcessor.java:237) at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor$ResourceRootHandler.access$100(BeanArchiveProcessor.java:206) at org.jboss.as.weld.deployment.processors.BeanArchiveProcessor.deploy(BeanArchiveProcessor.java:113) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165) ... 5 more Our jboss-deployment-structure.xml is as below. <?xml version="1.0" encoding="UTF-8"?> <jboss-deployment-structure> <ear-subdeployments-isolated>false</ear-subdeployments-isolated> <sub-deployment name="inner.war"> <dependencies> <module name="org.jboss.remote-naming"/> </dependencies> <resources> <resource-root path="APP-INF/lib/dep1.jar" /> <resource-root path="APP-INF/lib/dep2.jar" /> </resources> </sub-deployment> </jboss-deployment-structure> Our EAR structure is below, The same structure and jboss-deployment-structure.xml worked for us on JBOSS EAP 7. Is there any change in deployment structure? or is it a BUG? More details @ https://developer.jboss.org/message/980164#980164 -- This message was sent by Atlassian JIRA (v7.5.0#75005)