[jbossts-issues] [JBoss JIRA] Closed: (JBTM-612) check use of isDebugEnabled/debugAllowed

Jonathan Halliday (JIRA) jira-events at lists.jboss.org
Tue Nov 24 07:03:29 EST 2009


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

Jonathan Halliday closed JBTM-612.
----------------------------------

    Resolution: Done


> check use of isDebugEnabled/debugAllowed
> ----------------------------------------
>
>                 Key: JBTM-612
>                 URL: https://jira.jboss.org/jira/browse/JBTM-612
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Common
>    Affects Versions: 4.7.0
>            Reporter: Jonathan Halliday
>            Assignee: Jonathan Halliday
>             Fix For: 4.9.0
>
>
> The CLF exposes an rather complex API, in which isDebugEnabled and debugAllowed have different semantics. As pretty much everything is logged, the cost of these methods, and especially the cost of incorrect usage that leads to creating debug messages that just get throw away, is a non-trivial overhead. Both the implementation of these methods and their usage is suspect and needs a review.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbossts-issues mailing list