Start a conversation
  1. Savvion (Aurea Process) Support
  2. Aurea Process - Installation and Configuration
  3. Articles

Log files are not getting rolled forward on Aurea Process 2015 SP1

Overview

You are having issues on your Aurea Process (formerly known as CX Process, Savvion and SBM) 2015 SP1 server with log files not rolling over when they reach the maximum log file size as specified in the sbmlog.conf file.   This results in Aurea Process log files with sizes that are very large instead of multiple files with a maximum file size as specified in the sbmlog.conf file.

Prerequisites

  • You are running on Aurea Process 2015 SP1 on your server
  • Access to modify the Aurea Process sbmlog.conf file on the server

Solution

Note: The Aurea Process 2015 SP1 release has reached its end of life (EOL) as per the Aurea Product Support End of Life (EOL) Dates and Policy page.   It is recommended that you upgrade to a supported release of Aurea Process.

Diagnosis

Aurea Process uses the RollingFileAppender in log4j, which creates a lock on the log file to prevent the log file from being rolled forward.  When multiple JVMs are updating the same log file and each JVM's RollingFileAppender will create a lock to prevent any of the JVMs from rolling the log file forward.
This will occur for logs like the SBM log file because the EJB Server and the Portal Server will write updates to the same log file.

Workaround Steps

We have identified the following as a workaround for this issue, in the sbmlog.conf file, append the log file name with the token ${sbm.server.name} for all of the log files where the problem occurs. 
For example the following entry is for the sbm.log file:
log4j.appender.SBM.File=${sbm.home}/logs/sbm_${sbm.server.name}.log
At run-time, the token will get resolved to the values portalServer or ejbServer. This will create two separate log files for the EJB Server (sbm_ejbServer.log) and Portal server (sbm_portaServer.log), so multiple JVMs will not be accessing the same log file concurrently.

Testing

Once this workaround is applied the EJB Server will write to the sbm_ejbServer.log file and the Portal Server will write to the sbm_portalServer.log.  Both of these files will roll forward as they reach the default size limits

Choose files or drag and drop files
Was this article helpful?
Yes
No

  1. Priyanka Bhotika

  2. Posted

Comments