Bug 1160898

Summary:	The CLI command "read-boot-errors" does not include the timestamp of the error event
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Russell Dickenson <rdickens>
Component:	Domain Management	Assignee:	Emmanuel Hugonnet (ehsavoie) <ehugonne>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Kremensky <pkremens>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4.0	CC:	brian.stansberry, dandread, kkhan, myarboro
Target Milestone:	DR12
Target Release:	EAP 6.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-19 12:44:52 UTC	Type:	Enhancement
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Comment 1 Brian Stansberry 2014-11-05 23:08:09 UTC

I don't disagree, but note that these are *boot* errors. So they basically tell you of problems that occurred at boot, and the timestamps will all be roughly the same, telling you what time the server was booted.

It's not a general error log.

I don't think this qualifies as a Bug; more of an Enhancement.

Comment 3 JBoss JIRA Server 2014-11-28 13:30:01 UTC

Emmanuel Hugonnet <ehugonne> updated the status of jira WFCORE-274 to Coding In Progress

Comment 4 Emmanuel Hugonnet (ehsavoie) 2014-11-28 13:59:40 UTC

PR: https://github.com/jbossas/jboss-eap/pull/2097
Upstream PR: https://github.com/wildfly/wildfly-core/pull/368

Comment 7 Petr Kremensky 2014-12-05 13:57:58 UTC

Verified on EAP 6.4.0.DR12

"failure-timestamp" => 1417787387717L
println new Date(1417787387717L)
Fri Dec 05 14:49:47 CET 2014