[jbossts-issues] [JBoss JIRA] (JBTM-2950) LRA logging is wrong in pointing to tsLogger and using System.out
Tom Jenkinson (JIRA)
issues at jboss.org
Mon Jan 22 10:50:01 EST 2018
[ https://issues.jboss.org/browse/JBTM-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Jenkinson updated JBTM-2950:
--------------------------------
Fix Version/s: 5.7.2.Final
> LRA logging is wrong in pointing to tsLogger and using System.out
> -----------------------------------------------------------------
>
> Key: JBTM-2950
> URL: https://issues.jboss.org/browse/JBTM-2950
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: REST
> Affects Versions: 5.7.1.Final
> Reporter: Ondra Chaloupka
> Assignee: Ondra Chaloupka
> Fix For: 5.7.2.Final
>
>
> The LRA module uses inconsistent way of logging. Some parts uses the {{com.arjuna.ats.arjuna.logging}} which is wrong as it should define its own logger category to use in LRA. Other ones uses {{System.out|err}} for printing log information.
> Up to that there should be more consistency and more informative for user.
> * There are hidden reasons of some failures in some places.
> * The error messages get from the URL queries are unclear in some cases, e.g.
> {{not present: null: Cannont connect to an LRA coordinator: Connection refused}}
> (what does means {{not present}} and why {{null}}? this is a bit misguiding info which is not necessary to be part of the error message)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jbossts-issues
mailing list