[jboss-jira] [JBoss JIRA] (AS7-784) Remove deployment doesn't really remove it
Brian Stansberry (Resolved) (JIRA)
jira-events at lists.jboss.org
Tue Nov 1 16:46:45 EDT 2011
[ https://issues.jboss.org/browse/AS7-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Stansberry resolved AS7-784.
----------------------------------
Fix Version/s: No Release
(was: 7.1.0.Beta1)
Resolution: Won't Fix
I'm not going to try and fix this.
Conceivably, the scanner could maintain state of what it has deployed and if it detects that deployment is no longer in the server's deployment list, it could remove the deployment. So, I'd accept a really, really excellent patch (that includes extensive tests) from the community on this.
But the deployment scanner is already very complex logic, so I'm not going to solicit such a patch for what I consider to be an edge case. If this proves to be a problem for people we can revisit.
> 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: No Release
>
>
> 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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list