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

[Connor Penhale (JIRA)]

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

Connor Penhale edited comment on WFLY-1305 at 5/2/13 2:49 PM:
--------------------------------------------------------------

I have run into this issue as well, reproduced using approximately the same steps:

# In an AS 7.2.0.Final installation, standalone/deployments/ contains no applications or markers
# AS 7.2.0.Final is started (bin/standalone.sh)
# application-war.war is added to standalone/deployments/
# AS 7.2.0.Final deploys the application, and creates a .deployed marker
# AS 7.2.0.Final is stopped (jboss-cli.sh> connect, shutdown)
# application-war.war is modified to contain, for example, a missing dependency in jboss-deployment-structure.xml
# application-war.war is overwritten in standalone/deployments/ 
# Per README.txt, application-war.war.failed is removed, application-war.war.dodeploy is created
# AS 7.2.0.Final is started
# AS 7.2.0.Final fails to deploy the modified war
# No .failed marker is created, and the .dodeploy marker changes to .deployed marker
# CLI reports proper status (jboss-cli.sh> connect, deployment-info : STATUS=FAILED)

Please let the community know if additional information is required to help address this issue.

Thanks!
Connor
                
      was (Author: ol_cpenhale):
    I have run into this issue as well, reproduced using approximately the same steps:

# In an AS 7.2.0.Final installation, standalone/deployments/ contains no applications or markers
# AS 7.2.0.Final is started
# application-war.war is added to standalone/deployments/
# AS 7.2.0.Final deploys the application, and creates a .deployed marker
# AS 7.2.0.Final is stopped (jboss-cli.sh> connect, shutdown)
# application-war.war is modified to contain, for example, a missing dependency in jboss-deployment-structure.xml
# application-war.war is overwritten in standalone/deployments/ 
# Per README.txt, application-war.war.failed is removed, application-war.war.dodeploy is created
# AS 7.2.0.Final is started
# AS 7.2.0.Final fails to deploy the modified war
# No .failed marker is created, and the .dodeploy marker changes to .deployed marker
# CLI reports proper status (jboss-cli.sh> connect, deployment-info : STATUS=FAILED)

Please let the community know if additional information is required to help address this issue.

Thanks!
Connor
                  
> 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
>
> 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