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

David Lloyd (JIRA) jira-events at lists.jboss.org
Fri Feb 29 12:29:38 EST 2008

    [ http://jira.jboss.com/jira/browse/JBTM-331?page=comments#action_12400967 ] 
David Lloyd commented on JBTM-331:

I don't disagree - I also think that the level ought to be INFO.  But in this particular case, the type of message that is logged - a periodic success message - is more appropriate to TRACE in terms of the current logging "standard", as noted by Mark here - http://jira.jboss.com/jira/browse/JBTM-20#action_12346766

The guidelines I'd adhere to for JBossAS are:

1) An idle JBossAS should produce no logs (that's obviously the thrust of this issue)
2) Any logs that are generated on a per-request basis should be logged at level TRACE
3) Any one-time "debug" status messages (that are not repetitive in nature and do not grow in proportion to the number of requests) can be at DEBUG
4) INFO is OK for very low-volume, one-time messages like a greeting message "JBoss Foo version 2.0.0" or whatever

> 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