[jboss-jira] [JBoss JIRA] (AS7-784) Remove deployment doesn't really remove it
[
https://issues.jboss.org/browse/AS7-784?page=com.atlassian.jira.plugin.sy...
]
Brian Stansberry commented on AS7-784:
--------------------------------------
What I think I'll do here is remove the .deployed marker and put down a .skipdeploy
marker. This would happen whether the user did an 'undeploy' or a
'remove'. In both cases the scanner will put an INFO message in the logs noting
that the deployment has been updated or removed from the server via a means other than
manipulation of the filesystem.
Remove deployment doesn't really remove it
------------------------------------------
Key: AS7-784
URL: https://issues.jboss.org/browse/AS7-784
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.0.0.Beta3
Reporter: Stan Silvert
Assignee: Brian Stansberry
Fix For: 7.2.0.Alpha1
Steps:
1) Deploy something by copying an archive to the standalone/deployments directory.
2) Using the CLI or Console, remove the deployment.
i.e. /deployment=mywar.war/:remove
The deployment will stop, but the .war file and .deployed marker remain on the file
system. When you restart the server, mywar.war will deploy again.
The problem is that "remove" doesn't really remove. It only stops the
deployment until the next full restart. If you try to do some other operation on the
deployment you will get a NoSuchElementException.
And from the file system, it looks like the deployment is still deployed.
So we need to do something to fully "remove" the deployment. Perhaps we need
(yet another) marker file called .removed
--
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