Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Troubleshooting: Cannot start up system after log4j updates

Updated on May 7, 2019


With V4.1 SR2 and SP3, setting log4j logging attribute to DEBUG on all categories and on the root prevents the system from initializing.


  1. In log4j.xml, set priority values to DEBUG for all categories plus for the root.
  2. Start the server.
  3. System initialization fails, and FUA messages are written to PegaRULES log.


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.


Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us