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 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)