Bug 1145903 - [GSS] (6.3.2) Show more information of a timer in ERROR/WARN messages to identify the failed timer exactly
Summary: [GSS] (6.3.2) Show more information of a timer in ERROR/WARN messages to iden...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: EJB
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.3.2
Assignee: Jimmy Wilson
QA Contact: Jan Martiska
URL:
Whiteboard:
Depends On: 1145896
Blocks: eap632-blockers, eap632-payload
TreeView+ depends on / blocked
 
Reported: 2014-09-24 05:46 UTC by wfink
Modified: 2019-08-19 12:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1145896
Environment:
Last Closed: 2019-08-19 12:42:55 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-3888 0 Major Pull Request Sent Show more informations of a timer in ERROR/WARN messages to identify the failed timer exactly 2014-09-24 05:46:12 UTC

Description wfink 2014-09-24 05:46:10 UTC 
+++ This bug was initially created as a clone of Bug #1145896 +++

Description of problem:
Ti identify the exact Timer of a ERROR or WARN message exact informations are needed to identify the exact timer if an EJB handle more than one active timer at a time.

Therefore the full timer information should be shown in the logfile.
This should include the customized TimerInfo object where the application developer is able to add any needed information via the toString() implementation of this object.


Actual results:
In some cases only the timerId or less informations are shown.
Comment 2 wfink 2014-09-26 14:26:08 UTC 
PR to 6.3.x send
https://github.com/jbossas/jboss-eap/pull/1727
Comment 4 Jan Martiska 2014-10-16 11:35:26 UTC 
Verified in EAP 6.3.2.CR1.
Note You need to log in before you can comment on or make changes to this bug.