Sometimes Jboss server.log gets filled up with the below Periodic recovery first pass and second pass messages which is always annoying
DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] Periodic recovery – first pass <>
DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] StatusModule: first pass
DEBUG [com.arjuna.ats.txoj.logging.txojLoggerI18N] [com.arjuna.ats.internal.txoj.recovery.TORecoveryModule_3] – TORecoveryModule – first pass
DEBUG [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.recovery.info.firstpass] Local XARecoveryModule – first pass
DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] Periodic recovery – second pass <>
DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] AtomicActionRecoveryModule: Second pass
DEBUG [com.arjuna.ats.txoj.logging.txojLoggerI18N] [com.arjuna.ats.internal.txoj.recovery.TORecoveryModule_6] – TORecoveryModule – second pass
DEBUG [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.recovery.info.secondpass] Local XARecoveryModule – second pass
DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] Periodic recovery – first pass <>
How to solve this issue?
It is very easy all you have to do is add
<category name="com.arjuna"> <priority value="ERROR"/> </category>
To the jboss-log4j.xml, Before updating the file please take a backup.
Once done restart the Jboss server. You can also use value WARN or FATAL
Note:- It will pick up the new changes without restarting but it is always recommended to refresh the JVM once you make a configuration change.
The issue got fixed for me 🙂
admin