[
https://issues.jboss.org/browse/AS7-6526?page=com.atlassian.jira.plugin.s...
]
RH Bugzilla Integration commented on AS7-6526:
----------------------------------------------
Jan Martiska <jmartisk(a)redhat.com> made a comment on [bug
928922|https://bugzilla.redhat.com/show_bug.cgi?id=928922]
Verified that the enhancement is present in 6.1.0.ER5 and the logged message is much more
clear now.
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: EAP 6.1.0.Alpha (7.2.0.Final)
Reporter: Wolf-Dieter Fink
Assignee: Wolf-Dieter Fink
Priority: Minor
Fix For: 8.0.0.Alpha1
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