[jboss-jira] [JBoss JIRA] (AS7-3142) VirtualFile error messages

[narve2 (JIRA)]

    [ https://issues.jboss.org/browse/AS7-3142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680743#comment-12680743 ] 

narve2 commented on AS7-3142:
-----------------------------

Michael, that patch would be welcome - I've just spent some time finding out what that exception means. In my case, it was an ear-file with lots of jar-files in the lib directory. Apparently JBoss7 didn't like one particular jar-file, and failed with the above exception because of that. Don't know why yet, but probably because of strange class-path-entries in the manifest.mf-file of that jar-file. 

I tried to do the same changes you did, but unfortunately JBoss didn't compile from sources at my computer (despite it being based on maven!!), and I don't have time to figure out why :(
                
> VirtualFile error messages
> --------------------------
>
>                 Key: AS7-3142
>                 URL: https://issues.jboss.org/browse/AS7-3142
>             Project: Application Server 7
>          Issue Type: Enhancement
>          Components: VFS
>    Affects Versions: 7.1.0.CR1b
>         Environment: Windows 7, JDK 6, Eclipse Indigo
>            Reporter: Ben Software Engineer
>            Assignee: John Bailey
>
> I'm migrating an app from JBoss 5.0.1 to JBoss 7.1 and getting an error when starting deployment of the EAR.  It is almost impossible for me to troubleshoot as the error message is too vague.  Please add the virtual file name and any other information that would make this error useful, thank you.
> [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.subunit."xxx-ear.ear"."xxx.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."xxx-ear.ear"."xxx.war".PARSE: Failed to process phase PARSE of subdeployment "oflows.war" of deployment "xxx-ear.ear"
> 	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b]
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
> 	at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
> Caused by: java.lang.IllegalArgumentException: Given parent is not an ancestor of this virtual file
> 	at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:116)
> 	at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> 	at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> 	at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> 	at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> 	at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> 	at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> 	at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> 	at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> 	at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:122)
> 	at org.jboss.vfs.VirtualFile.getPathNameRelativeTo(VirtualFile.java:110)
> 	at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processTlds(TldParsingDeploymentProcessor.java:105)
> 	at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.deploy(TldParsingDeploymentProcessor.java:81)
> 	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b]
> 	... 5 more

--
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