[jbossts-issues] [JBoss JIRA] Closed: (JBTM-733) streamline debug level logging

Jonathan Halliday (JIRA) jira-events at lists.jboss.org
Thu Apr 8 05:44:37 EDT 2010

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

Jonathan Halliday closed JBTM-733.

    Resolution: Done

> streamline debug level logging
> ------------------------------
>                 Key: JBTM-733
>                 URL: https://jira.jboss.org/jira/browse/JBTM-733
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Common, Configuration
>    Affects Versions: 4.10.0
>            Reporter: Jonathan Halliday
>            Assignee: Jonathan Halliday
>             Fix For: 4.11.0
> The debug level logging in JBossTS is unnecessarily complex. DebugLevel values other than 0xffffffff ('ON') and 0x00000000 ('OFF'), FacilityCode and VisibilityLevel filters are largely unused. In practice the use case for debug level logging is for customers to pass trace information back to support. In such cases we inevitably want everything and will filter it later with grep according to the case at hand. The additional verbosity that DebugLevel, FacilityCode and VisibilityLevel add to the codebase is unwarranted. These classes should be nuked. Removing this added complexity will also help make the transition to the new common JBoss logging system (TAG-3) easier.

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