[
https://issues.jboss.org/browse/WFLY-8909?page=com.atlassian.jira.plugin....
]
Matthew Casperson updated WFLY-8909:
------------------------------------
Steps to Reproduce:
Steps to reproduce:
1. Deploy WAR file to domain controller
2. Assign the WAR file to a server group, but disable it
3. Update the contents of the WAR file via the CLI tool i.e. deploy --force myApp.war
4. Most of the time the deployment in the existing server group is enabled (it seems that
very occasionally the deployment remains disabled)
I would not expect that updating the file in the content repository would enable a
disabled deployment in a server group.
was:
Steps to reproduce:
1. Deploy WAR file to domain controller
2. Assign the WAR file to a server group, but disable it
3. Update the contents of the WAR file via the CLI tool i.e. deploy --force myApp.war
4. Most of the time the deployment in the existing server group is enabled (it seems that
very occasionally the deployment remains disabled)
I would not expect that updating the file in the content repository would change the
enable a disabled deployment in a server group.
Disabled deployments in server group enabled after WAR is updated
-----------------------------------------------------------------
Key: WFLY-8909
URL:
https://issues.jboss.org/browse/WFLY-8909
Project: WildFly
Issue Type: Bug
Components: Server
Affects Versions: 11.0.0.Alpha1
Environment: Centos 7
OpenJDK
Reporter: Matthew Casperson
Assignee: Jason Greene
Updating the contents of a WAR file in a domain controller content repository will
usually lead to a disabled deployment in a server group being enabled.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)