2:31 p.m.
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
Affects Versions: 7.0.0.Beta3
Reporter: Stan Silvert
Assignee: Brian Stansberry
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:13 p.m.
New subject: [JBoss JIRA] Commented: (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:
--------------------------------------
I'd rather just have the CLI operation fail (or be unavailable), if there was a clean
way to do it. If you're using the FS scanner to manage your deployments, you're
turning over management of the deployment to the scanner.
There's probably not a clean way to do it though. :(
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
Affects Versions: 7.0.0.Beta3
Reporter: Stan Silvert
Assignee: Brian Stansberry
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:35 a.m.
New subject: [JBoss JIRA] Updated: (AS7-784) Remove deployment doesn't really remove it
[
https://issues.jboss.org/browse/AS7-784?page=com.atlassian.jira.plugin.sy...
]
Brian Stansberry updated AS7-784:
---------------------------------
Fix Version/s: 7.0.0.CR1
Component/s: Domain Management
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.0.0.CR1
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:15 a.m.
New subject: [JBoss JIRA] Updated: (AS7-784) Remove deployment doesn't really remove it
[
https://issues.jboss.org/browse/AS7-784?page=com.atlassian.jira.plugin.sy...
]
Brian Stansberry updated AS7-784:
---------------------------------
Fix Version/s: 7.1.0.Beta2
(was: 7.0.0.CR1)
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.1.0.Beta2
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:46 p.m.
New subject: [JBoss JIRA] (AS7-784) Remove deployment doesn't really remove it
[
https://issues.jboss.org/browse/AS7-784?page=com.atlassian.jira.plugin.sy...
]
David Lloyd commented on AS7-784:
---------------------------------
If this isn't resolvable, can we close it with the appropriate resolution?
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.1.0.Beta1
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
3:46 p.m.
New subject: [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 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
4 p.m.
New subject: [JBoss JIRA] (AS7-784) Remove deployment doesn't really remove it
[
https://issues.jboss.org/browse/AS7-784?page=com.atlassian.jira.plugin.sy...
]
Stan Silvert reopened AS7-784:
------------------------------
In that case, I think we need to go back to Brian's original comment and throw an
error if you try to remove a file-managed deployment via a management operation.
As it is now, there is no way for the console to know if a deployment can be removed or
not. It's really not such an edge case to think that a user will see the deployment
in the console and try to remove it.
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
8:58 p.m.
New subject: [JBoss JIRA] (AS7-784) Remove deployment doesn't really remove it
[
https://issues.jboss.org/browse/AS7-784?page=com.atlassian.jira.plugin.sy...
]
Jason Greene updated AS7-784:
-----------------------------
Fix Version/s: Open To Community
(was: No Release)
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: Open To Community
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
9:30 p.m.
New subject: [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 updated AS7-784:
---------------------------------
Fix Version/s: 7.2.0.Alpha1
(was: Open To Community)
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
9:34 p.m.
New subject: [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
9:59 p.m.
New subject: [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 edited comment on AS7-784 at 9/13/12 10:58 PM:
----------------------------------------------------------------
What I think I'll do here is remove the .deployed marker and put down a .undeployed
marker, which should prevent further scanning. 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.
was (Author: brian.stansberry):
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
4313
days inactive
4801
days old
10 comments
6 participants
participants (6)
-
Brian Stansberry (JIRA) -
Brian Stansberry (Resolved) (JIRA)
-
David Lloyd (Commented) (JIRA)
-
Jason Greene (Updated) (JIRA)
-
Stan Silvert (JIRA)
-
Stan Silvert (Reopened) (JIRA)