[jboss-jira] [JBoss JIRA] (AS7-4780) Incorrect status report when missing services are no longer needed

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/AS7-4780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated AS7-4780:
----------------------------------

    Fix Version/s:     (was: 7.1.4.Final (EAP))

    
> Incorrect status report when missing services are no longer needed
> ------------------------------------------------------------------
>
>                 Key: AS7-4780
>                 URL: https://issues.jboss.org/browse/AS7-4780
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Domain Management
>    Affects Versions: 7.1.2.Final (EAP)
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>            Priority: Minor
>             Fix For: 7.2.0.Alpha1
>
>
> If a service is missing, that gets recorded when detected (e.g. at boot):
> 16:28:50,626 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014775:    New missing/unsatisfied dependencies:
>       service jboss.remoting.endpoint.subsystem (missing) dependents: [service jboss.naming.remote, service jboss.ejb3.localEjbReceiver.value, service jboss.ejb3.connector, service jboss.ejb3.localEjbReceiver.reference] 
>       service jboss.remoting.server.remoting-connector (missing) dependents: [service jboss.ejb.remoting.connector.client-mapping-entry-provider-service, service jboss.ejb3.connector] 
> But then at shutdown, when the service is no longer required, the status report says it is "(new available)" instead of the expected "(no longer required)"
> 16:46:06,776 INFO  [org.jboss.as.controller] JBAS014774: Service status report
> JBAS014776:    Newly corrected services:
>       service jboss.remoting.endpoint.subsystem (new available)
>       service jboss.remoting.server.remoting-connector (new available)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira