[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=12797127#comment-12797127 ] 

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

Brad Maxwell <bmaxwell at redhat.com> made a comment on [bug 997583|https://bugzilla.redhat.com/show_bug.cgi?id=997583]

Description of problem:

Deploy via copying file into deployments directory, where it has an xml needing a resource that does not exist causes it to fail because of missing dependencies.  A .failed marker file is created.  Restart the server and the .failed becomes a .deployed even though it is really still failed and not accessible.

Version-Release number of selected component (if applicable):

JBoss EAP 6.1.0

How reproducible:


Steps to Reproduce:
1. deploy jboss-as-kitchensink-jsp.war which needs java:jboss/datasources/KitchensinkJSPQuickstartDS, which if you don't define will cause this:

JBAS014775: New missing/unsatisfied dependencies:
service jboss.naming.context.java.jboss.datasources.KitchensinkJSPQuickstartDS (missing) dependents: service jboss.persistenceunit."jboss-as-kitchensink-jsp.war#primary"

2. see that it creates a jboss-as-kitchensink-jsp.war.failed

3. Restart the JBoss server, it will then have jboss-as-kitchensink-jsp.war.deployed, however it still logs the missing dependencies and the war is not accessible because it is failed, though the marker file does not indicate this.

4. see that a .deployed marker file is created even though it is actually failed

Actual results:

After restart a .deployed marker file exists even though it is missing dependencies and is not accessible

Expected results:

After restart there is still a .failed marker file 

Additional info:

Looks to be the same issue as described in WFLY-1305

a file-scanner deployment that fails on boot will not be undeployed after failure
https://issues.jboss.org/browse/WFLY-1305
                
> 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