[jboss-jira] [JBoss JIRA] (WFLY-1305) a file-scanner deployment that fails on boot will not be undeployed after failure

[Chao Wang (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chao Wang updated WFLY-1305:
----------------------------

    Attachment: operation-outcome.xml


Attach an operation outcome which tried to deploy test.war(simply missing module dependency) during server start-up under ParallelBootOperationContext, seems like composite steps roll-back does not function properly. Moreover, on a running server, deployment after deploument-scanner "remove-then-add" action works fine, in that case, it used OperationContextImpl.
                
> a file-scanner deployment that fails on boot will not be undeployed after failure
> ---------------------------------------------------------------------------------
>
>                 Key: WFLY-1305
>                 URL: https://issues.jboss.org/browse/WFLY-1305
>             Project: WildFly
>          Issue Type: Bug
>            Reporter: Toby Crawley
>            Assignee: Chao Wang
>         Attachments: operation-outcome.xml
>
>
> When an app is deployed via the deployments/ dir, but fails for some reason, it is marked as failed with a .failed marker and undeployed. When the AS is rebooted, it tries to redeploy the failure. If this deploy also fails, this new deployment *isn't* undeployed, and a .deployed marker is written to deployments.
> This is with the 7.2.0.Final used in Immutant, I've yet to try to build Immutant on top of 8.x.

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