Description of problem: If a deployment failed then the file "<app>.war.failed" generated so after fixing the the problem when we restart the EAP, it will fail with below Error because the "<app>.war.failed" file is present in deployment directory : ----------------------- 10:35:03,485 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 18) JBAS014613: Operation ("add") failed - address: ([("deployment" => "Test.war")]) - failure description: "JBAS014803: Duplicate resource [(\"deployment\" => \"Test.war\")]" 10:35:03,487 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) "JBAS014784: Failed executing subsystem deployment-scanner boot operations" 10:35:03,493 FATAL [org.jboss.as.server] (Controller Boot Thread) JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. ----------------------- Version-Release number of selected component (if applicable): How reproducible: - Below are the steps to reproduce the issue : Steps to Reproduce: 1. deploy a "Test.war" 2. Change something in "Test.war" to fail it. 3. "Test.war.failed" file will be created. 4. stop JBoss EAP. 5. Revert the changes done in "Test.war" so that it will deploy successfully. 6. Now there are two files ("Test.war.failed" and "Test.war")in deployment directory. 7. Restart JBoss EAP, it will fail with below Error : ----------------------- 10:35:03,485 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 18) JBAS014613: Operation ("add") failed - address: ([("deployment" => "Test.war")]) - failure description: "JBAS014803: Duplicate resource [(\"deployment\" => \"Test.war\")]" 10:35:03,487 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) "JBAS014784: Failed executing subsystem deployment-scanner boot operations" 10:35:03,493 FATAL [org.jboss.as.server] (Controller Boot Thread) JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. ----------------------- Actual results: Expected results: Additional info:
"Deploy" but how? Dropping the file? Via the CLI? Via the Console? From inside Eclipse? (the last one works for me, many times a day actually) Also, why stopping the server to fix the deployment? Does the same happen if the Server is kept on? All this said, the scanner should ignore/remove the .failed marker file if the timestamp of the .?ar file is newer. Reassigning to Carlo for proper component selection (this BZ is misfiled).
Problem is introduced in https://issues.jboss.org/browse/AS7-2581 https://github.com/wildfly/wildfly-core/blob/1.0.0.Alpha13/deployment-scanner/src/main/java/org/jboss/as/server/deployment/scanner/FileSystemDeploymentService.java#L670 forces a retry a the failed deployment (via the marker file). https://github.com/wildfly/wildfly-core/blob/1.0.0.Alpha13/deployment-scanner/src/main/java/org/jboss/as/server/deployment/scanner/FileSystemDeploymentService.java#L703 forces a deployment because the deployment file is newer than the marker file.
qa_acking, qa contact can stay as it is, will be properly assigned when CP01 arrives.
Verified in EAP 6.4.1.CR2.
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.