Bug 1169239
Summary: | Startup fails with 'JBAS014803: Duplicate resource' if "<app>.war.failed" file is present in deployment folder | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Swapnil Chaudhari <schaudha> |
Component: | Server | Assignee: | Chao Wang <chaowan> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Jan Martiska <jmartisk> |
Severity: | high | Docs Contact: | eap-docs <eap-docs> |
Priority: | unspecified | ||
Version: | 6.3.0 | CC: | bbaranow, chaowan, jason.greene, jawilson, jmartisk, pslavice, rsvoboda, schaudha |
Target Milestone: | CR2 | ||
Target Release: | EAP 6.4.1 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | Type: | Bug | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1207953 |
Description
Swapnil Chaudhari
2014-12-01 06:20:56 UTC
"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. Retroactively bulk-closing issues from released EAP 6.4 cummulative patches. |