Skip to main content

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.

Support Article

Log file does not roll over



The log file does not roll over.

Error Messages

Not Applicable

Steps to Reproduce


Root Cause

A defect or configuration issue in the operating environment.

The default behavior for the out-of-the-box prlog4j2.xml settings for the file appender is as below,

<RollingRandomAccessFile  name="PEGA" fileName="${sys:pega.logdir}/PegaRULES.log" filePattern="${sys:pega.logdir}/PegaRULES-%d{MM-dd-yyyy}-%i.log.gz">
      <Pattern>%d [%20.20t] [%10.10X{pegathread}] [%20.20X{tenantid}] [%20.20X{app}] (%30.30c{3}) %-5p %X{stack} %X{userid} - %m%n</Pattern>
           <!--Deny message logged under ALERT log level-->
           <ThresholdFilter level="ALERT" onMatch="DENY" onMismatch="NEUTRAL"/>
           <TimeBasedTriggeringPolicy />
           <SizeBasedTriggeringPolicy size="250 MB"/>
    <DefaultRolloverStrategy max="20"/>


Here’s the explanation for the reported behavior:

In the above configuration, there is no time based policy and the roll over point is 250 MB.

Modify the configuration as per requirement (refer to the documentation on the Apache log4js website).

Published March 22, 2019 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration 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.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us