[JBoss JIRA] Created: (JBTM-331) Reduce the log level of the periodic recovery stuff
by David Lloyd (JIRA)
Reduce the log level of the periodic recovery stuff
---------------------------------------------------
Key: JBTM-331
URL: http://jira.jboss.com/jira/browse/JBTM-331
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Recovery
Reporter: David Lloyd
The JBossAS log (as of 5.0.0.Beta4) is filled with this kind of thing:
2008-02-28 17:57:51,703 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] Periodic recovery - second pass <Thu, 28 Feb 2008 17:57:51>
2008-02-28 17:57:51,703 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] AtomicActionRecoveryModule: Second pass
2008-02-28 17:57:51,703 DEBUG [com.arjuna.ats.txoj.logging.txojLoggerI18N] [com.arjuna.ats.internal.txoj.recovery.TORecoveryModule_6] - TORecoveryModule - second pass
2008-02-28 17:57:51,703 DEBUG [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.recovery.info.secondpass] Local XARecoveryModule - second pass
2008-02-28 17:59:51,703 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] Periodic recovery - first pass <Thu, 28 Feb 2008 17:59:51>
2008-02-28 17:59:51,704 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] StatusModule: first pass
2008-02-28 17:59:51,704 DEBUG [com.arjuna.ats.txoj.logging.txojLoggerI18N] [com.arjuna.ats.internal.txoj.recovery.TORecoveryModule_3] - TORecoveryModule - first pass
2008-02-28 17:59:51,704 DEBUG [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.recovery.info.firstpass] Local XARecoveryModule - first pass
These messages ought to be at TRACE level. The first hint is that this is the only thing spamming the log after successful startup. Also on more than one occasion, folks pop into the public #jboss IRC channel asking about why their logs get spammed with these messages. An otherwise idle JBossAS instance quietly gobbles 750kb of disk space a day with these messages.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months
[JBoss JIRA] Created: (JBTM-380) update log4j to mach JBossAS
by Jonathan Halliday (JIRA)
update log4j to mach JBossAS
----------------------------
Key: JBTM-380
URL: http://jira.jboss.com/jira/browse/JBTM-380
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Application Server Integration
Affects Versions: 4.3.0.GA
Reporter: Jonathan Halliday
Assigned To: Jonathan Halliday
Fix For: 4.4.CR1
JBossAS uses a slightly different log4j release from the one we have. Although it's only a point release it does contain a public API change (Level.TRACE) which can cause problems with certain classpath settings. Upgrade JBossTS to use the same log4j.jar as the app server, thus eliminating this annoyance.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 5 months