Excessive Logging Generated by the Time Slicing Sync Job Following Release 16.4.1 Upgrade

Products

• Clarity PPM SaaS
• Clarity PPM On Premise
• Clarity FedRAMP

Issue/Introduction

Following an upgrade to Clarity release 16.4.1, the cmn_sch_job_logs database table experiences rapid and significant growth. This increase in database size is caused by excessive log entries being generated by the Time Slicing Sync job during routine executions.

Steps to Reproduce: 

1. Schedule and execute the Time Slicing Sync job with debugging disabled.
2. Once the job completes, query the cmn_sch_job_logs table for the most recent runs.
3. Observe the volume of records generated by the job execution.

Expected Results: No routine log entries should be written to the cmn_sch_job_logs table when debugging is disabled.

Actual Results: An excessive number of entries are logged per execution, causing the cmn_sch_job_logs table to grow substantially over time. Table CMN_SCH_JOB_LOGS has the following information logged.

TimeSliceSyncTimesheetActualsSlicer: No timesheets selected for processing (resp is null or empty)
TimeSliceSyncTimesheetActualsSlicer: Starting process() method

Environment

Clarity 16.4.1

Cause

DE184020

Resolution

Fixed in

• Clarity 16.4.2
• Clarity 16.4.1 Patch 1 (16.4.1.1)