Bug 1074999
| Summary: | Application disappears from Manage Deployments section of EAP console | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Tomas David <tdavid> |
| Component: | Domain Management | Assignee: | Emmanuel Hugonnet (ehsavoie) <ehugonne> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Petr Kremensky <pkremens> |
| Severity: | medium | Docs Contact: | Russell Dickenson <rdickens> |
| Priority: | unspecified | ||
| Version: | 6.1.1 | CC: | dereed, ehugonne, emuckenh, kkhan, smumford |
| Target Milestone: | ER5 | ||
| Target Release: | EAP 6.3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
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.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-06-28 15:39:19 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Tomas David
2014-03-11 10:46:29 UTC
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 PR: https://github.com/jbossas/jboss-eap/pull/1309 *** Bug 1040493 has been marked as a duplicate of this bug. *** Verified on EAP 6.3.0.ER7 |