[jbossts-issues] [JBoss JIRA] Updated: (JBTM-263) improve logging robustness

Andrew Dinn (JIRA) jira-events at lists.jboss.org
Tue Dec 9 12:03:47 EST 2008

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

Andrew Dinn updated JBTM-263:

    Fix Version/s: future
                       (was: 4.5)

This needs some proper tooling. I have a script which finds orphaned messages (see JBTM-450 for results of running it)  but it needs further work. This is being punted to a later release for now.

> improve logging robustness
> --------------------------
>                 Key: JBTM-263
>                 URL: https://jira.jboss.org/jira/browse/JBTM-263
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Common
>    Affects Versions: 4.2.3.SP5
>            Reporter: Jonathan Halliday
>            Assignee: Andrew Dinn
>            Priority: Minor
>             Fix For: future
> Some @message tags are in normal comments rather than javadoc comments, so they don't get processed into message bundles. Some are missing entirely. It should be possible to develop tooling to detect these at build time by checking against log statements in the code. Also, make the logging more robust in the case where errors are missing - a generic message should be printed in preference to crashing as sometimes happens now. See also JBTM-231.

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