[JBoss JIRA] (JBTM-2040) Remove some noisy logging that adds no value
- First Post
- Replies
- Stats
-
Go to
- ----- 2025 -----
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2008 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2007 -----
- December
- November
- October
- September
- August
- July
- June
- May
[
https://issues.jboss.org/browse/JBTM-2040?page=com.atlassian.jira.plugin....
]
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
4054
days inactive
4054
days old
jbossts-issues@lists.jboss.org
0 comments
1 participants
tags (0)
participants (1)
-
Paul Robinson (JIRA)