Bug 928922 – [AS7-6526] It is difficult to identify an EJB Timer with the logged timer-id, especially if it is non persistent

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 928922 - [AS7-6526] It is difficult to identify an EJB Timer with the logged timer-id, especially if it is non persistent

Summary:	[AS7-6526] It is difficult to identify an EJB Timer with the logged timer-id,...

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	JBoss Enterprise Application Platform 6
Classification:	JBoss
Component:	EJB (Show other bugs)
Sub Component:
Version:	6.0.1
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	ER5
Target Release:	EAP 6.1.0
Assigned To:	Jaikiran Pai
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	929052
	Show dependency tree / graph

Reported:	2013-03-28 14:05 EDT by Brad Maxwell
Modified:	2013-10-23 19:02 EDT (History)
CC List:	4 users (show)

See Also:
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:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
JBoss Issue Tracker	AS7-6526	Minor	Resolved	It is difficult to identify an EJB Timer with the logged timer-id, especially if it is non persistent	2014-09-04 14:45:22 EDT

Groups: None (edit)

Description Brad Maxwell 2013-03-28 14:05:30 EDT

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 03:24:45 EDT

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 14:43:50 EDT

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

Note You need to log in before you can comment on or make changes to this bug.