How to turn off log4j errors at Thor Xellerate server startup
Originally Published: 2005-02-02
Last Modified: 2023-09-22
Article Number
Applies To
Issue
The out-of-the-box installation of Thor Xellerate produces the following error messages when the xlserver, xlobject, and xlclient startup:
WARN Ignoring Property Logger.LogFile.MaxBackupIndex because it is not a valid property
WARN Ignoring Property Logger.LogFile.MaxFile.Size because it is not a valid property
Cause
Resolution
#Logger.LogFile.MaxFileSize=10MB
log4j.appender.LogFile.MaxFileSize=10MB
#Logger.LogFile.MaxBackupIndex=5
log4j.appender.LogFile.MaxBackupIndex=5
Related Articles
FIM - Log4j memory leak Number of Views Enterprise Manager Log settings: EM.log - log4j.xml Number of Views Old connector Log4j files not removed in RSA Governance & Lifecycle Number of Views The audit.log is not logging to the proper location defined in the log4j.xml Number of Views RSA-2024-08: RSA Governance and Lifecycle Critical Security Update for Unauthenticated JMX Agent and Older Version of Log4… Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to verify NTP server synchronization is not working in RSA Authentication Manager 8.x RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?
