[
https://issues.jboss.org/browse/AS7-762?page=com.atlassian.jira.plugin.sy...
]
Heiko Braun commented on AS7-762:
---------------------------------
David:
dmlloyd: it could work one of two ways
[3:10pm] dmlloyd: it could block until the container is "stable", which is to
say that no changes will happen in the container without user intervention
[3:10pm] dmlloyd: on a server startup, this would be after the whole server starts (when
the first status report is logged in the log file)
[3:11pm] dmlloyd: the other way it could work is to return right away with the current
status and a flag indicating whether the state is transient or stable
[3:11pm] magesh left the chat room.
[3:11pm] dmlloyd: the risk there is you can get false positives for errors as services are
often installed out-of-order
Provide an operation to request service status report after server
has been started
-------------------------------------------------------------------------------------
Key: AS7-762
URL:
https://issues.jboss.org/browse/AS7-762
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Reporter: Heiko Braun
Assignee: Brian Stansberry
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 is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira