1 2 Previous Next 18 Replies Latest reply on Dec 4, 2013 5:05 AM by Thomas Jenkinson

    Can these log lines be removed?

    Paul Robinson Master


      The following log lines appear a lot when TRACE is enabled for 'com.arjuna':


      6562013-11-29 08:08:14,893 TRACE [com.arjuna.ats.jta] (EJB default - 1) BaseTransaction.getStatus
      662013-11-28 11:42:00,005 TRACE [com.arjuna.ats.jta] (EJB default - 5) TransactionSynchronizationRegistryImple.getTransactionKey
      662013-11-28 11:35:17,532 TRACE [com.arjuna.ats.jta] (ServerService Thread Pool – 56) TransactionImpleManager.suspend
      5442013-11-28 11:35:15,926 TRACE [com.arjuna.ats.jta] (ServerService Thread Pool – 52) TransactionSynchronizationRegistryImple.getTransactionStatus


      A total of almost 1,200 lines combined for those three messages after running a single transaction. This makes it a pain to read through the logs as you need to fight through pages of these statements.

      The Transaction Analyser could filter out these lines programmatically (and it does IIRC). However, this tool is just doing what a user would have to if they where diagnosing such issues without tooling support. It's also a pain for developers working on this tool, as they have to work a lot with the logs to automate the analysis process.

      I don't think they provide any value in their current form. Can they either be removed or improved?

      See here for Jira issue: [JBTM-2040] Remove some noisy logging that adds no value - JBoss Issue Tracker

        1 2 Previous Next