Synchronize Agile Central Job to Failing if a Project is locked

book

Article ID: 140151

calendar_today

Updated On:

Products

CLARITY PPM FOR ITG CLARITY PPM FEDERAL Clarity PPM On Premise

Issue/Introduction

When running the Synchronize Agile Central job the job is failing due to a locked project linked to Agile System Integration.

STEPS TO REPRODUCE

1. Successfully sync a project to a working Agile System Integration
2. Navigate to the same project
3. Click on the Task tab
4. Click on Gantt
5. Edit a task to lock the project
6. Exit the Gantt view without saving
7. Log out of CA PPM
8. Log back in to CA PPM without Unlocking the project
9. Run the Synchronize Agile Central job

 

Expected Results:
The Synchronize Agile Central job should complete successfully.

Actual Results:
The Synchronize Agile Central job is failing with the following error:
 
Processing Synchronize Agile Central . Time: Thu Jan 24 10:04:04 PST 2019Job Started 1/24/19 12:04 PM 
Warning 1/24/19 12:04 PM 
Error Occurred java.lang.NumberFormatException: For input string: "projmgr.COULD_NOT_LOCK_PROJECT_UPDATE"
Warning 1/24/19 12:04 PM 
Job Failed :
Job Completed 1/24/19 12:04 PM 
NJS-0401: Execution of job failed.
Warning 1/24/19 12:04 PM 
There was a problem updating CA PPM project:<project_name>
400
projmgr.COULD_NOT_LOCK_PROJECT_UPDATE
PRJ-07002: Update operation failed. The project cannot be locked.
Message 1/24/19 12:04 PM 
Finished processing Synchronize Agile Central . Time: Thu Jan 24 10:04:13 PST 2019

Cause

This is caused by Defect DE46753

Environment

Clarity PPM 15.4, 15.4.1, 15.5, 15.5.1

Resolution

A solution for this Bug is provided in Clarity PPM version 15.6


The Synchronize Agile Central job was failing when it found a project that was locked by project managers performing updates. 

The job should skip locked projects and keep processing all other projects that are marked to be synchronized, but are not locked.  

We do not want to unlock projects that are locked by project managers, even if they are locked by mistake. 

Next time the job runs if the project is unlocked it will be processed as usual since the sync flag remains marked for the failing project.


Fix: Modified the synchronization to treat the exception that is thrown by the REST API when it attempts to update a project that is locked. 

The job will still finish as failed but it will process all other projects marked to sync that are not locked.