My Oracle Support Banner

FAQ: RPM.LOG Grows Exponentially Causing Server Space to Be Utilized 100% After Applying Patch 27839881 (Doc ID 2431040.1)

Last updated on AUGUST 02, 2018

Applies to:

Oracle Retail Price Management - Version 16.0.1 and later
Information in this document applies to any platform.

Purpose

 This article addresses questions regarding the new Log4J2 upgrade.

Questions and Answers

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Questions and Answers
  The RPM.LOG grows exponentially causing server space to be utilized 100% since
applying <Patch 27839881>. The application updates RPM.LOG file at a different location ($ORACLE_HOME/USER_PROJECTS/domains/RPM_DOMAIN/@DOMAIN.HOME@/servers/@wls.target@/logs/RPM.LOG). The log level is verbose.
 Is there any way to enforce size limit parameter the way it was for older log4j log file?

<param name="MaxFileSize" value="1024KB" />
              <param name="MaxBackupIndex" value="10" />
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.