[jboss-jira] [JBoss JIRA] (WFLY-2028) An exploded war inside an archived ear returns 404

Thomas Frühbeck (JIRA) jira-events at lists.jboss.org
Tue Sep 17 17:51:04 EDT 2013


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

Thomas Frühbeck commented on WFLY-2028:
---------------------------------------

this change completely nukes exploded deployments (e.g. as in JBossTools) 

 private Closeable exportExplodedWar(final boolean war, final VirtualFile file) throws IOException {
        if (war && !file.isFile()) {
            File warContent = file.getPhysicalFile();
            VFSUtils.recursiveCopy(file, warContent.getParentFile());
 
seems to completly overwrite the files with itself.
If write protecting files in deployment, below exception is thrown:

23:09:29,392 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."mssms-ear.ear".STRUCTURE: org.jboss.msc.service.Sta
rtException in service jboss.deployment.unit."mssms-ear.ear".STRUCTURE: JBAS018733: Failed to process phase STRUCTURE of deployment "mssms-ear.ear"
        at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1944) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1877) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_40]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_40]
        at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011060: Failed to process children for EAR ["/work/java/wildfly-8.0.0.Beta1-SNAPSHOT/standalone/deplo
yments/mssms-ear.ear"]
        at org.jboss.as.ee.structure.EarStructureProcessor.deploy(EarStructureProcessor.java:237)
        at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
        ... 5 more
Caused by: java.io.FileNotFoundException: /work/java/wildfly-8.0.0.Beta1-SNAPSHOT/standalone/deployments/mssms-ear.ear/mssms.war/css/test.css (Keine Berechtigung)
        at java.io.FileOutputStream.open(Native Method) [rt.jar:1.7.0_40]
        at java.io.FileOutputStream.<init>(FileOutputStream.java:221) [rt.jar:1.7.0_40]
        at java.io.FileOutputStream.<init>(FileOutputStream.java:171) [rt.jar:1.7.0_40]
        at org.jboss.vfs.VFSUtils.recursiveCopy(VFSUtils.java:725)
        at org.jboss.vfs.VFSUtils.recursiveCopy(VFSUtils.java:722)
        at org.jboss.vfs.VFSUtils.recursiveCopy(VFSUtils.java:722)
        at org.jboss.as.ee.structure.EarStructureProcessor.exportExplodedWar(EarStructureProcessor.java:277)
        at org.jboss.as.ee.structure.EarStructureProcessor.createResourceRoot(EarStructureProcessor.java:261)
        at org.jboss.as.ee.structure.EarStructureProcessor.deploy(EarStructureProcessor.java:192)
        ... 6 more

                
> An exploded war inside an archived ear returns 404
> --------------------------------------------------
>
>                 Key: WFLY-2028
>                 URL: https://issues.jboss.org/browse/WFLY-2028
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: EE
>    Affects Versions: 8.0.0.Alpha4
>            Reporter: Emmanuel Hugonnet
>            Assignee: Emmanuel Hugonnet
>
> When an archived ear which includes an exploded war is deployed in EAP 6, the application seems to be deployed successfully but it returns status code 404. 
> 1. Start EAP 6 standalone mode
> 2. Put the attached test.ear to $JBOSS_HOME/standalone/deployments
> 3. Access the web application
>     curl -v http://localhost:8080/test/index.jsp 
> JBoss returns status code 404.
> JBoss returns actual response of web application's content.
> Additional info:
> Same application works in EAP 5. When an application is an exploded ear which includes an exploded war, it works in EAP 6.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the jboss-jira mailing list