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
Enterprise Manager Log settings: EM.log - log4j.xml 54Number of Views The audit.log is not logging to the proper location defined in the log4j.xml 26Number of Views Old connector Log4j files not removed in RSA Governance & Lifecycle 50Number of Views FIM - Log4j memory leak 27Number of Views RSA-2024-08: RSA Governance and Lifecycle Critical Security Update for Unauthenticated JMX Agent and Older Version of Log4… 49Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA RADIUS Server service failed to start in the RSA Authentication Manager 8.1 Operations Console Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Release Notes: Cloud Access Service and RSA Authenticators
Don't see what you're looking for?