[jbossts-issues] [JBoss JIRA] (JBTM-2040) Remove some noisy logging that adds no value
Paul Robinson (JIRA)
jira-events at lists.jboss.org
Fri Nov 29 03:18:05 EST 2013
[ https://issues.jboss.org/browse/JBTM-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Robinson updated JBTM-2040:
--------------------------------
Description:
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.
was:
The following log lines appear _a lot_ when TRACE is enabled for 'com.arjuna'
2013-11-28 11:42:00,005 TRACE [com.arjuna.ats.jta] (EJB default - 5) TransactionSynchronizationRegistryImple.getTransactionKey
2013-11-28 11:35:17,532 TRACE [com.arjuna.ats.jta] (ServerService Thread Pool -- 56) TransactionImpleManager.suspend
2013-11-28 11:35:15,926 TRACE [com.arjuna.ats.jta] (ServerService Thread Pool -- 52) TransactionSynchronizationRegistryImple.getTransactionStatus
A total of almost 10,000 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.
> 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
>
>
> 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
More information about the jbossts-issues
mailing list