[jbossts-issues] [JBoss JIRA] (JBTM-2040) Remove some noisy logging that adds no value
[
https://issues.jboss.org/browse/JBTM-2040?page=com.atlassian.jira.plugin....
]
Paul Robinson commented on JBTM-2040:
-------------------------------------
TRACE logging is needed by the Transaction Analyser to gather its data, so the level
can't be changed.
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 figure work a lot with the logs to automate the analysis process.
Remove some noisy logging that adds no value
--------------------------------------------
Key: JBTM-2040
URL: https://issues.jboss.org/browse/JBTM-2040
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: JTA
Reporter: Paul Robinson
Assignee: Tom Jenkinson
Fix For: 5.0.0.CR2, 4.17.17
Attachments: server.log
The following log lines appear _a lot_ when TRACE is enabled for 'com.arjuna'
||Count||Message
|656|2013-11-29 08:08:14,893 TRACE [com.arjuna.ats.jta] (EJB default - 1)
BaseTransaction.getStatus
|66|2013-11-28 11:42:00,005 TRACE [com.arjuna.ats.jta] (EJB default - 5)
TransactionSynchronizationRegistryImple.getTransactionKey
|66|2013-11-28 11:35:17,532 TRACE [com.arjuna.ats.jta] (ServerService Thread Pool -- 56)
TransactionImpleManager.suspend
|544|2013-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.
I don't think they provide any value in their current form. Can they either be
removed or improved?
See the attached log for an example.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira