[
https://issues.jboss.org/browse/WFLY-1305?page=com.atlassian.jira.plugin....
]
Brian Stansberry commented on WFLY-1305:
----------------------------------------
It's not undeployed because the management ops created by the scanner are inserted
into the list of boot ops, and boot ops do not roll back on failure.
I'm not sure why the .deployed file is written instead of a .failed file, since even
though the ops don't roll back, they still failed. Figuring that out will hopefully
point to an overall solution.
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