Bug 928922

Summary:	[AS7-6526] It is difficult to identify an EJB Timer with the logged timer-id, especially if it is non persistent
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Brad Maxwell <bmaxwell>
Component:	EJB	Assignee:	Jaikiran Pai <jpai>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.0.1	CC:	brian.stansberry, dimitris, jawilson, jmartisk
Target Milestone:	ER5
Target Release:	EAP 6.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	929052

Description Brad Maxwell 2013-03-28 18:05:30 UTC

It is difficult to identify an EJB Timer with the logged timer-id, especially if it is non persistent 

The JBAS14143 message and other skip messages log the timer id, but this is not very helpful as it is complicated to find the related application bean if the timer is persistent or not possible if it is a non persistent timer.

https://issues.jboss.org/browse/AS7-6526

Comment 6 Jan Martiska 2013-04-19 07:24:45 UTC

Verified that the enhancement is present in 6.1.0.ER5 and the logged message is much more clear now.

Comment 9 mark yarborough 2013-07-23 18:43:50 UTC

Details inside vpn: https://post-office.corp.redhat.com/mailman/private/eap-pm-list/2013-July/msg00105.html