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

Michael Bannister (JIRA) jira-events at lists.jboss.org
Fri Mar 16 21:58:47 EDT 2012 

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

Michael Bannister commented on AS7-3142:
----------------------------------------

I get same thing as original reporter - so I grabbed master codebase, added an extra try/catch in TldParsingDeploymentProcessor to capture a bit more info and found this - note the first *Caused by* line:

{code}

01:28:02,515 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.subunit."myapp.ear"."mywebapp.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."myapp.ear"."mywebapp.war".PARSE: Failed to process phase PARSE of subdeployment "mywebapp.war" of deployment "myapp.ear"
	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
	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) [classes.jar:1.6.0_29]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_29]
	at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_29]
Caused by: java.lang.IllegalArgumentException: file was /content/myapp.ear/spring-webmvc-3.0.5.RELEASE.jar/META-INF/spring.tld and root was /content/myapp.ear/mywebapp.war
	at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processTlds(TldParsingDeploymentProcessor.java:114)
	at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.deploy(TldParsingDeploymentProcessor.java:83)
	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
	... 5 more
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:110)
	at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processTlds(TldParsingDeploymentProcessor.java:108)
	... 7 more
{code}

My EAR contains two 'skinny' WARs (but with taglib-containing jars included) and lots of other JARs at the root of the EAR, referenced by the {{Class-Path}} in the manifest of the WARs which depend on them.

{code}
myapp.ear
  mywebapp.war
    META-INF/MANIFEST.MF
      Class-Path: spring-core-3.0.5.RELEASE.jar spring-webmvc-3.0.5.RELEASE.jar ...
    WEB-INF/lib
      spring-security-taglibs-3.0.5.RELEASE.jar
      spring-webmvc-3.0.5.RELEASE.jar
  
  myotherwebapp.war
    ...
  
  spring-core-3.0.5.RELEASE.jar
  spring-security-taglibs-3.0.5.RELEASE.jar
  spring-webmvc-3.0.5.RELEASE.jar
  ...
{code}

So, it seems that the error above is grumbling because it's found a TLD referenced in the webapp which is not packaged inside it.  I don't understand the context in which the TldParsingDeploymentProcessor is run, so I'm not sure whether it's right to throw an error.  That said, the error could certainly be improved by catching the IllegalArgumentException - if I get time I'll find out how to file a patch or whatever the procedure is for JBoss contribs...
                
> 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

More information about the jboss-jira mailing list