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

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-5644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated WFLY-5644:
-----------------------------------
    Fix Version/s: 11.0.0.Alpha1


> 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
>             Fix For: 11.0.0.Alpha1
>
>
> 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)