[jboss-jira] [JBoss JIRA] (WFLY-188) It is difficult to identify an EJB Timer with the logged timer-id, especially if it is non persistent

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792037#comment-12792037 ] 

RH Bugzilla Integration commented on WFLY-188:
----------------------------------------------

mark yarborough <myarboro at redhat.com> changed the Status of [bug 928922|https://bugzilla.redhat.com/show_bug.cgi?id=928922] from VERIFIED to CLOSED
                
> It is difficult to identify an EJB Timer with the logged timer-id, especially if it is non persistent
> -----------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-188
>                 URL: https://issues.jboss.org/browse/WFLY-188
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB
>            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