In previous versions of JBoss EAP 6, the status of a deployment was not updated on the filesystem when the console was used.
As a consequence, using both the filesystem scanner and the console to manage the status of a deployment resulted in the scanner believing the deployment to be undeployed.
This release of the product enables the console and the filesystem scanner to share the status of the deployment and users can now use both administrative tools to manage deployments.
Description of problem:
Application disappears from Manage Deployments section of EAP console after reenabling the application and after server restart.
Version-Release number of selected component (if applicable):
Always when application is disabled -> enabled -> and server is restarted.
Steps to Reproduce:
1. Unzip jboss-eap-6.1.1.zip. Create management user. Copy some Application.war into jboss-eap-6.1/standalone/deployments. Create file Application.war.dodeploy in the same folder.
2. Start standalone server.
3. Open EAP console -> Manage Deployments. Disable application. Enable application (After this Application.war.undeployed should be replaced with Application.war.deployed in jboss-eap-6.1/standalone/deployments folder).
4. Restart standalone server.
5. Open EAP console -> Manage Deployments.
Application disappears from Manage Deployments section of EAP console.
Application.war.undeployed file is present in jboss-eap-6.1/standalone/deployments folder.
Application is still visible in Manage Deployments section of EAP console.
Application.war.deployed file is present in jboss-eap-6.1/standalone/deployments folder.
My experience (with 6.2.0) is different from the description. After disabling and then re-enabling the application, I don't see Application.war.deployed; I still see Application.war.undeployed.
That explains why it doesn't get deployed after restart.
I see also Application.war.undeployed after step 3. In brackets I described what I am expecting after step 3.
Upstream PR : https://github.com/wildfly/wildfly/pull/6117
PR : https://github.com/jbossas/jboss-eap/pull/1179
Setting this back to assigned since it caused https://bugzilla.redhat.com/show_bug.cgi?id=1092355 which was raised as a potential beta blocker. To get around this the commit for https://bugzilla.redhat.com/show_bug.cgi?id=1092355 was reverted on the 6.x branch and also in the 'special' branch used for ER3 containing just ER2 and beta blockers: https://github.com/jbossas/jboss-eap/tree/EAP_6.3.0.ER3-dev
Upstream PR : https://github.com/wildfly/wildfly/pull/6220
*** Bug 1040493 has been marked as a duplicate of this bug. ***
Verified on EAP 6.3.0.ER7