[jboss-jira] [JBoss JIRA] (WFLY-5644) EJB timers should use a different logging category to separate it from other EJB invocations

[Wolf-Dieter Fink (JIRA)]

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

Wolf-Dieter Fink commented on WFLY-5644:
----------------------------------------

--  Text for the release note --
Logging enhancement for EJB timer.
Timer services can now use a separate category "org.jboss.as.ejb3.timer" to track timer events in DEBUG or TRACE level without affecting the complete EJB logging.
The message identifiers (i.e. WFLYEJB0022) remain the same as before.

> EJB timers should use a different logging category to separate it from other EJB invocations
> --------------------------------------------------------------------------------------------
>
>                 Key: WFLY-5644
>                 URL: https://issues.jboss.org/browse/WFLY-5644
>             Project: WildFly
>          Issue Type: Feature Request
>            Reporter: Wolf-Dieter Fink
>            Assignee: Wolf-Dieter Fink
>              Labels: ejb, timer, timers, timerservice
>
> To analyze timer behaviour or track issues related to timers sometimes a log level higher than INFO is needed.
> Unfortunately the category "org.jboss.as.ejb3" does not make a differenciation and setting this category to DEBUG or TRACE cause a high amount of log messages, this can have performance impacts and make it dfficult to handle and read the logfiles.
> It should be possible to have a separate category for timers.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)