Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-1982

Use logger to log all the exception stacktraces instead of several Exception.printStackTrace() calls which uses the stdout

    Details

    • Type: Feature Request
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 4.17.10
    • Fix Version/s: None
    • Component/s: JTA, JTS
    • Labels:
      None

      Description

      The arjuna code uses pattern e.printStackTrace() on several places in the code. This would be better to be changed for a logger would be used.

      For ArjunaJTA I counted 28 (excluding tests) places where the logger is not used and I suppose it should be.

      Secondary. It would be nice in case of the XAException the error code would be printed together with the exception stacktrace. I have one example where I would appreciated it for example.
      It's ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java
      method handleOrphan where after the xares.rollback(xid) is called the exception is printed to stdout + log does not contain the error code.

      This issue was moved from https://bugzilla.redhat.com/show_bug.cgi?id=1007384.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                ochaloup Ondrej Chaloupka
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: