frank moss created AS7-4348: ------------------------------- Summary: deployment fails on jboss 7 with generic message. Key: AS7-4348 URL: https://issues.jboss.org/browse/AS7-4348 Project: Application Server 7 Issue Type: Bug Reporter: frank moss https://community.jboss.org/message/726171#726171 4:11:44,831 INFO [org.jboss.as.connector] (MSC service thread 1-1) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final) 14:11:46,814 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) 14:11:46,819 INFO [org.jboss.as.naming] (MSC service thread 1-8) JBAS011802: Starting Naming Service 14:11:46,829 INFO [org.jboss.as.mail.extension] (MSC service thread 1-8) JBAS015400: Bound mail session [java:jboss/mail/Default] 14:11:46,874 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBo...skipping... 13:26:53,012 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry servlet-api-2.5.jar in "/content/testing.war/WEB-INF/lib/google-api-client-extensions-1.6.0-beta.jar" does not point to a valid jar for a Class-Path reference. 13:26:53,013 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry httpclient-4.0.3.jar in "/content/testing.war/WEB-INF/lib/google-api-client-extensions-1.6.0-beta.jar" does not point to a valid jar for a Class-Path reference. 13:26:53,014 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry commons-logging-1.1.1.jar in "/content/testing.war/WEB-INF/lib/google-api-client-extensions-1.6.0-beta.jar" does not point to a valid jar for a Class-Path reference. 13:26:53,015 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry ridl.jar in "/content/testing.war/WEB-INF/lib/juh-3.2.1.jar" does not point to a valid jar for a Class-Path reference. 13:26:53,017 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry jurt.jar in "/content/testing.war/WEB-INF/lib/juh-3.2.1.jar" does not point to a valid jar for a Class-Path reference. 13:26:54,083 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: Failed to start service jboss.deployment.unit."testing.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."testing.war".STRUCTURE: Failed to process phase STRUCTURE of deployment "testing.war" 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_30] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30] 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: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:162) [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 13:26:54,093 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment testing.war in 0ms 13:26:54,093 INFO [org.jboss.as.server] (HttpManagementService-threads - 6) JBAS015870: Deploy of deployment "testing.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"testing.war\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"testing.war\".STRUCTURE: Failed to process phase STRUCTURE of deployment \"testing.war\""}} 13:26:54,095 INFO [org.jboss.as.controller] (HttpManagementService-threads - 6) JBAS014774: Service status report JBAS014777: Services which failed to start: service jboss.deployment.unit."testing.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."testing.war".STRUCTURE: Failed to process phase STRUCTURE of deployment "testing.war" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira