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

[RH Bugzilla Integration (JIRA)]

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

RH Bugzilla Integration commented on WFLY-1305:
-----------------------------------------------

Chao Wang <chaowan at redhat.com> changed the Status of [bug 997583|https://bugzilla.redhat.com/show_bug.cgi?id=997583] from NEW to POST

> 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
>      Security Level: Public(Everyone can see) 
>            Reporter: Toby Crawley
>            Assignee: Chao Wang
>             Fix For: 8.0.0.Beta1
>
>         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 was sent by Atlassian JIRA
(v6.2.6#6264)