Issue

• Suppose application(app-1.war) is deployed with a runtime name app.war. Now we can deploy the next version as app-2.war (same runtime name) in a disabled state using the --disabled option. Then use replace-deployment command to swap the two applications. At this point, app-1.war is now displayed as not added in the deployment-info command. The replace deployment worked, I can see that the new application (app-2.war) started picking up the requests to the runtime name. When we attempt to undeploy app-1.war, then requests to app-2.war are also rejected with 404s even though deployment-info shows that the application should be fine. To resolve this, I need to undeploy app-2.war using --keep-content and redeploy.

Steps to replicate issue:
1. Start EAP 6.4.4 in domain mode and deploy application using following CLI command:

[domain@localhost:9999 /] deploy /NotBackedUp/Delete/ClusterWebApp-1.war --server-groups=main-server-group --name=ClusterWebApp-1.war --runtime-name=ClusterWebApp-1.war

1. Deploy second version of application in "disabled" state with same "runtime-name"

[domain@localhost:9999 /] deploy /NotBackedUp/Delete/ClusterWebApp-2.war --disabled --name=ClusterWebApp-2.war --runtime-name=ClusterWebApp-1.war 

1. Now use replace-deployment command to access latest version of application:

[domain@localhost:9999 /] /server-group=main-server-group:replace-deployment(name=ClusterWebApp-2.war,to-replace=ClusterWebApp-1.war)

1. Now try to undeploy old version of application

/server-group=main-server-group/deployment=ClusterWebApp-1.war:undeploy()

After undploying older version we are not able to access(404) latest version of application(ClusterWebApp-2.war) as well.To access it we have to redeploy it.