[
https://issues.jboss.org/browse/AS7-6526?page=com.atlassian.jira.plugin.s...
]
Wolf-Dieter Fink edited comment on AS7-6526 at 2/15/13 9:42 AM:
----------------------------------------------------------------
Add the timedObjectId (app.module.bean) for message JBAS14143.
Create JBAS14262 if the timer is in retry state and the scheduled invocation is skipped.
was (Author: wdfink):
Add the timedObjectId (app.module.bean) for message JBAS14143.
Create JBAS14144 if the timer is in retry state and the scheduled invocation is skipped.
It is difficult to identify an EJB Timer with the logged timer-id,
especially if it is non persistent
-----------------------------------------------------------------------------------------------------
Key: AS7-6526
URL:
https://issues.jboss.org/browse/AS7-6526
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.2.0.Alpha1
Reporter: Wolf-Dieter Fink
Assignee: Wolf-Dieter Fink
Priority: Minor
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira