[
https://issues.jboss.org/browse/WFCORE-1392?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-1392:
------------------------------------------
[~soul2zimate] No, that check is necessary. The other classes have it too, but it's
inside the call to DeploymentHandlerUtil.deploy().
I don't regard this as a bug; the background content repo cleaner task is meant to
clean up the repo when edge cases like this occur.
Undeploy doesn't remove Data content if server is in
--admin-only mode
-----------------------------------------------------------------------
Key: WFCORE-1392
URL:
https://issues.jboss.org/browse/WFCORE-1392
Project: WildFly Core
Issue Type: Bug
Components: Server
Affects Versions: 2.1.0.CR2
Reporter: Chao Wang
Assignee: Jason Greene
{noformat}
Steps to Reproduce:
1. Start server instance using --admin-only flag
2. Deploy application using CLI command.
~~~
deploy /valid/path/WebApp.war --runtime-name=WebApp.war --name=WebApp.war
~~~
3. Undeploy application using CLI command:
~~~
undeploy WebApp.war
~~~
4. Application will be undeployed but content from 'data' directory are not
removed.
{noformat}
Lines:
https://github.com/wildfly/wildfly-core/blob/b1a4439f442f7984e681840c0f8d...
https://github.com/wildfly/wildfly-core/blob/e737eff554ee433ca54835154fd6...
runningMode value is ADMIN_ONLY will bypass that step in DeploymentRemoveHandler.java
leads to this behavior.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)