[
https://issues.jboss.org/browse/WFLY-543?page=com.atlassian.jira.plugin.s...
]
RH Bugzilla Integration commented on WFLY-543:
----------------------------------------------
Rostislav Svoboda <rsvoboda(a)redhat.com> made a comment on [bug
980219|https://bugzilla.redhat.com/show_bug.cgi?id=980219]
I think this will need to go through Change Request Procedure to get into EAP 6.2.0.
It's new functionality/enhancements.
Only some users would be allowed to read this data - probably additional item to test with
RBAC in EAP 6.2.0.
Provide an operation to request service status report after server
has been started
-------------------------------------------------------------------------------------
Key: WFLY-543
URL:
https://issues.jboss.org/browse/WFLY-543
Project: WildFly
Issue Type: Feature Request
Components: Domain Management
Reporter: Heiko Braun
Labels: console_prio
Fix For: 8.0.0.Beta1
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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira