Troubleshooting: Cannot start up system after log4j updates
Symptom
With V4.1 SR2 and SP3, setting log4j logging attribute to DEBUG on all categories and on the root prevents the system from initializing.
Example:
- In
log4j.xml
, set priority values to DEBUG for all categories plus for the root. - Start the server.
- System initialization fails, and FUA messages are written to PegaRULES log.
Solution
This behavior was reproduced on v4.1 SR2 Tomcat and v4.1 SP3 Websphere systems.
The problem is alleviated by removing the DEBUG priority setting from the root.