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,...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: EJB
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER5
: EAP 6.1.0
Assignee: Jaikiran Pai
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 929052
TreeView+ depends on / blocked
 
Reported: 2013-03-28 18:05 UTC by Brad Maxwell
Modified: 2019-03-22 07:04 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker AS7-6526 0 Minor Resolved It is difficult to identify an EJB Timer with the logged timer-id, especially if it is non persistent 2014-09-04 18:45:22 UTC

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
Note You need to log in before you can comment on or make changes to this bug.