Bug 980219 - [GSS](6.4.0) Ability to read boot errors via the admin APIs
Summary: [GSS](6.4.0) Ability to read boot errors via the admin APIs
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Domain Management
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: DR2
: EAP 6.4.0
Assignee: Brian Stansberry
QA Contact: Petr Kremensky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-01 18:46 UTC by Brian Stansberry
Modified: 2019-08-19 12:43 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-19 12:38:37 UTC
Type: Feature Request
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1140118 0 unspecified CLOSED [Doc Feature] Include information Read Boot Errors using the Management CLI 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker EAP6-160 0 Major Closed Ability to read boot errors via the admin APIs 2017-07-28 23:09:58 UTC
Red Hat Issue Tracker WFLY-543 0 Major Resolved Provide an operation to request service status report after server has been started 2017-07-28 23:09:58 UTC

Internal Links: 1140118

Description Brian Stansberry 2013-07-01 18:46:37 UTC 
If a server starts but reported errors during boot, there is no way to access the error data via the management API and users are reduced to grepping the logs. This information needs to be captured and stored for later reporting.
Comment 2 Rostislav Svoboda 2013-08-26 10:50:23 UTC 
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.
Comment 3 Rostislav Svoboda 2013-08-28 09:05:51 UTC 
Setting qa_ack to - for now. If it goes through Change Request Procedure happy to change it to +.
Comment 6 Petr Kremensky 2014-01-22 13:59:35 UTC 
Same situation as with EAP 6.2.0. Setting qa_ack to - for now.
Comment 7 JBoss JIRA Server 2014-08-22 08:20:53 UTC 
Emmanuel Hugonnet <ehugonne> updated the status of jira WFLY-543 to Coding In Progress
Comment 8 Kabir Khan 2014-09-17 19:39:58 UTC 
https://github.com/jbossas/jboss-eap/pull/1692
Comment 9 Petr Kremensky 2014-09-29 08:20:56 UTC 
Verified on EAP 6.4.0.DR2
Comment 15 Mike Millson 2015-03-12 13:57:11 UTC 
Am I correct in my understanding:

1. The PR was made for this:
https://github.com/jbossas/jboss-eap/pull/1692 

2. We have removed this from the EAP 6.4.0 documentation.

3. The functionality will be there in EAP 6.4.0, but we are not testing/supporting this in EAP 6.4.0, and that if we want this supported we need to open an RFE to get this officially added.

Is that right?
Comment 18 JBoss JIRA Server 2015-04-28 15:04:13 UTC 
John Doyle <jdoyle> updated the status of jira EAP6-160 to Closed
Note You need to log in before you can comment on or make changes to this bug.