[jbossts-issues] [JBoss JIRA] Commented: (JBTM-331) Reduce the log level of the periodic recovery stuff

Jonathan Halliday (JIRA) jira-events at lists.jboss.org
Fri Feb 29 08:58:58 EST 2008

    [ http://jira.jboss.com/jira/browse/JBTM-331?page=comments#action_12400944 ] 
Jonathan Halliday commented on JBTM-331:

See http://jira.jboss.com/jira/browse/JBTM-20?page=all for the backstory on this. We already downgrade this stuff from INFO to DEBUG when running integrated with the AS. The arjuna level won't be changed, so the options are to change the global rewriting of arjuna messages in AS from INFO->DEBUG to INFO->TRACE which will impact other messages too, or install a filter in log4j. Why is AS even logging at DEBUG by default? It should be INFO, at least for production releases.

> 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


More information about the jbossts-issues mailing list