How to turn off log4j errors at Thor Xellerate server startup
Originally Published: 2005-02-02
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
The audit.log is not logging to the proper location defined in the log4j.xml 23Number of Views Enterprise Manager Log settings: EM.log - log4j.xml 54Number of Views FIM - Log4j memory leak 27Number of Views RSA Customer Advisory: Apache Vulnerability Log4j2 CVE-2021-44228 170Number of Views Old connector Log4j files not removed in RSA Governance & Lifecycle 49Number of Views
Trending Articles
Troubleshooting RSA SecurID Access Identity Router to RSA Authentication Manager test connection failures RSA SecurID Software Token 5.0.2 Downloads for Microsoft Windows RSA Authentication Manager 8.9 Release Notes (January 2026) Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.8 Setup and Configuration Guide
Don't see what you're looking for?