PAS for OpenEdge uses two separate logging frameworks depending on which component generates the log:
Component Framework Configured in
Tomcat server logs Logback logging-tomcat.properties
PAS for OpenEdge application logs Logback logging-pasoe.properties
ABL application agent logs OpenEdge Logger openedge.properties

Tomcat and application log rollover

The log files defined in logging-tomcat.properties and logging-pasoe.properties adhere to the Logback framework. By default, the log file name definition may include {yyyy-MM-dd} and optionally .{HH-mm-ss}, where {yyyy-MM-dd} indicates that the log file rolls over at the start of each day. The .{HH-mm-ss} component is not mandatory.

When the agentLogMaxSize property is enabled, the agent log file automatically follows the naming pattern <abl_app_name>.agent.<date>.<time>.log, even if the time component is not explicitly specified, ensuring that every rollover—whether date-based or size-based—produces a unique filename.

Log file rollover means the component of the instance stops writing to one log file and begins writing to a new log file.

ABL application agent log rollover

Unlike Tomcat and application-level logs, which use the Logback framework, the ABL application agent log is generated by the MS Agent process (_mproapsv) and uses the OpenEdge Logger framework. As a result, its rollover behavior is configured separately in <instance-name>/conf/openedge.properties rather than in the Logback properties files.

The ABL agent log filename and path is specified using the agentLogFile property.

agentLogFile=${catalina.base}/logs/<abl_app_name>.agent.{yyyy-MM-dd}.{HH-mm-ss}.log
With this pattern, rollovers create files such as:
oepas1.agent.2026-04-10.08-15-32.log
oepas1.agent.2026-04-10.14-47-05.log
oepas1.agent.2026-04-11.00-00-09.log
Note: Use HH (24-hour clock), not hh (12-hour clock), to avoid duplicate filenames when rollovers occur before and after noon.

Rollover triggers

The ABL application agent log can support two managed rollover triggers:
  • Size-based rollover is active when agentLogMaxSize > 0.
  • Date-based rollover is active when agentLogFile includes an explicit date token such as {yyyy-MM-dd}.

When both are active, the session manager evaluates both triggers and whichever condition is met first causes the rollover.

Trigger Condition Result
Size-based Active log file reaches or exceeds agentLogMaxSize Rollover occurs once the file size exceeds the configured value; new file gets the same date and a new HH-mm-ss timestamp.
Date-based Midnight arrives before the size threshold is reached Rollover occurs at midnight; new file gets the next calendar date and timestamp.

Date-based rollover occurs once per day, whereas size-based rollover (controlled by agentLogMaxSize) can occur multiple times within the same day, especially when verbose logging is active or when the size limit is set to a low value.

When agentLogMaxSize=0 (the default), size-based rollover is disabled. Date-based rollover applies only when agentLogFile includes an explicit date token such as, {yyyy-MM-dd}.

If agentLogFile is a literal filename such as, ${catalina.base}/logs/oepas1.agent.log, the agent continues to use that static file and no date is added automatically.

For property definitions, valid ranges, and out-of-range behavior, see agentLogMaxSize in Configure OpenEdge properties.

Behaviour at PAS for OpenEdge restart

When managed rollover is enabled, the session manager evaluates the most recent agent log file for the current day before deciding whether to create a new file or append to an existing one.

If agentLogFile is a literal static filename and agentLogMaxSize=0, the configured file is used directly and no date-based file lookup is performed.
Condition at startup Action
No log file exists for today Creates a new log file
Most recent log file for today is below agentLogMaxSize Appends to the existing file; no new file is created
Most recent log file for today is at or above agentLogMaxSize Performs a rollover and creates a new file

The action taken on the agent log file at startup also depends on how the PAS for OpenEdge instance is started or restarted:

  • tcman pasoestart -I <instance_name> -restart—Older agent log files are removed and a new log file is created when the MS Agent starts.
  • tcman -stop -I <instance name> followed by tcman -clean followed by tcman pasoestart -I <instance_name> -start—Older agent log files are removed and a new log file is created when the MS Agent starts.
  • tcman -stop -I <instance name> followed by tcman -clean -A followed by tcman pasoestart -I <instance_name> -start—The -A flag preserves existing log files by archiving rather than removing them. When the MS Agent starts, the session manager evaluates the most recent agent log file for the current day:
    Condition at startup Action
    Most recent log file for today is at or above agentLogMaxSize Archives the existing file; creates a new log file
    Most recent log file for today is below agentLogMaxSize Appends to the existing file; no new file is created

    When agentLogMaxSize=0, the session manager always appends to the most recent log file for today if one exists.

Log file retention

You can limit the number of agent log files that accumulate on disk using the agentLogMaxHistory property. After each rollover, the session manager scans the logs directory and deletes the oldest agent log files for that ABL application until the file count does not exceed the configured value.

When agentLogMaxHistory=0 (the default), no files are deleted and log files accumulate indefinitely.

Retention is scoped per ABL application—log files belonging to other ABL applications on the same PAS for OpenEdge instance are not affected.

For the property definition and valid range, see agentLogMaxHistory in Configure OpenEdge properties.

Example configuration

The following example configures the ABL application agent log to roll over when the active file reaches 500 MB and to retain a maximum of 20 log files:
[AppServer.SessMgr.oepas1]
agentLogFile=${catalina.base}/logs/oepas1.agent.{yyyy-MM-dd}.{HH-mm-ss}.log
agentLogMaxSize=500
agentLogMaxHistory=20