[jboss-jira] [JBoss JIRA] (WFLY-3980) Web UI shows deployments active after undeploying dependencies

Stanley Hillner (JIRA) issues at jboss.org
Wed Oct 15 05:28:35 EDT 2014


Stanley Hillner created WFLY-3980:
-------------------------------------

             Summary: Web UI shows deployments active after undeploying dependencies
                 Key: WFLY-3980
                 URL: https://issues.jboss.org/browse/WFLY-3980
             Project: WildFly
          Issue Type: Bug
          Components: Web Console
    Affects Versions: 8.1.0.Final, 8.0.0.Final
            Reporter: Stanley Hillner
            Assignee: Heiko Braun
            Priority: Minor


If you undeploy a dependency of an application, the application with the dependency is still marked active in the web UI.

Consider the following applications being deployed while an arrow represents a dependency:
* xyz-api.jar
* xyz-impl.jar -> xyz-api.jar
* xyz-ui.war -> xyz-api.jar, xyz-impl.jar

If you now undeploy xyz-api.jar the log output says something like this:
{noformat}
JBAS014775:    New missing/unsatisfied dependencies:
      service jboss.module.spec.service."deployment.xyz-api.jar".main (missing) dependents: [service jboss.module.resolve.phase."deployment.xyz-impl.jar".main.1, service jboss.module.resolve.phase."deployment.xyz-ui.war".main.1, service jboss.module.service."deployment.xyz-impl.jar".main, service jboss.module.service."deployment.xyz-ui.war".main] 
      service module.resolved.service."deployment.xyz-impl.jar".main (missing) dependents: [service jboss.module.service."deployment.xyz-impl.jar".main] 
      service module.resolved.service."deployment.xyz-ui.war".main (missing) dependents: [service jboss.module.service."deployment.xyz-ui.war".main]
{noformat}

This behavior is correct since xyz-ui.war is also no longer reachable and undertow returns a 404 page for it.

*But in the web UI (Runtime > Manage Deployments) the deployments xyz-impl.jar and xyz-ui.war are still marked active with the checkmark besides them.*

I think this is a bug because it indicates a wrong state to the administrators.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


More information about the jboss-jira mailing list