[jboss-jira] [JBoss JIRA] (WFCORE-66) Provide an operation to request service status report after server has been started

Emmanuel Hugonnet (JIRA) issues at jboss.org
Fri Aug 22 04:23:00 EDT 2014


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

Emmanuel Hugonnet moved WFLY-543 to WFCORE-66:
----------------------------------------------

          Project: WildFly Core  (was: WildFly)
              Key: WFCORE-66  (was: WFLY-543)
      Component/s: Domain Management
                       (was: Domain Management)
    Fix Version/s:     (was: 9.0.0.CR1)


> Provide an operation to request  service status report  after server has been started
> -------------------------------------------------------------------------------------
>
>                 Key: WFCORE-66
>                 URL: https://issues.jboss.org/browse/WFCORE-66
>             Project: WildFly Core
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Domain Management
>            Reporter: Heiko Braun
>            Assignee: Emmanuel Hugonnet
>              Labels: console_prio
>
> For proper healthcare it would beneficial if I could verify the server status after it has been started. I.e. to catch these, which currently only appear in the server log:
> [Server:server-three] 17:48:26,636 INFO  [org.jboss.as.server] (MSC service thread 1-2) Service status report
> [Server:server-three]    New missing/unsatisfied dependencies:
> [Server:server-three]       service jboss.binding.http2 (missing)
> [Server:server-three] 
> [Server:server-three] 17:48:26,636 ERROR [org.jboss.as] (MSC service thread 1-4) JBoss AS 7.0.0.Beta4-SNAPSHOT "(TBD)" started (with errors) in 3893ms - Started 101 of 149 services (1 services failed or missing dependencies, 47 services are passive or on-demand)



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


More information about the jboss-jira mailing list