Time Slicing job deadlock error - due to OWB save

book

Article ID: 187119

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

Frequently seeing that Time Slicing job is getting a deadlock error when using Open Workbench (OWB). 

Cause

In this scenario, the Time Slicing jobs fails due to an attempted save to a project via Clarity Open Workbench (presumably a large project which can take a few seconds to save).
action=schedulers.GetSavePrecheckRequest&externalSource=CA+PPM+Workbench 
 
Another action could be an update to the team also presumably on a  larger project which can take a few seconds to complete.
action:projmgr.teamUpdate 

Environment

Release : Any

Component : CLARITY TIME SLICING

Resolution

These deadlocks are ok to ignore and as per design, Time Slicing, will always be a victim and will catch up on the next run.
 
Rescheduling the job to run every minute instead of 5 minutes can help as well - in case the job fails in one run, in the next minute there can be a successful run.

Additional Information

See also: Time Slicing job failures - troubleshooting / known causes