Process fails intermittently with Lock prImportExport in logs
search cancel

Process fails intermittently with Lock prImportExport in logs


Article ID: 103089


Updated On:


Clarity PPM On Premise


The process fails only sometimes and it is not consistent in the behavior. When the process step that has erroed out when selected and retried it error is rectified without making any changes to the process. What is causing this intermittent issue?

BG-CA log shows exception: 

<XOGOutput xmlns:xsi="" xsi:noNamespaceSchemaLocation="../xsd/status.xsd"> 
<Object type="project"/> 
<Status elapsedTime="0.285 seconds" state="FAILURE"/> 
<Statistics failureRecords="1" insertedRecords="0" totalNumberOfRecords="1" updatedRecords="0"/> 
<column name="ID">5009348</column> 
<column name="name">R-00235767 On Semiconductor Co</column> 
<column name="UNIQUE_NAME">129996</column> 
<Description>Project Object update failed</Description> 
java.lang.Exception: 31 

APP-CA log shows error:

WARN 2018-06-11 13:03:57,731 [http-nio-14001-exec-4] niku.xql2 (clarity:admin:12321440__75C0B6B8-7859-4270-BD78-692C266B1F88:XOG::project::write) Lock prImportExport held by user 1 requested by user 1 
WARN 2018-06-11 13:03:57,731 [http-nio-14001-exec-4] niku.schedulers (clarity:admin:12321440__75C0B6B8-7859-4270-BD78-692C266B1F88:XOG::project::write) ImportProjectProcessor.doProcess(): Project (ID=5009348) is locked by another user! 
ERROR 2018-06-11 13:03:57,732 [http-nio-14001-exec-4] niku.xql2 (clarity:admin:12321440__75C0B6B8-7859-4270-BD78-692C266B1F88:XOG::project::write) Failure while evaluating "xogprojectapi($PROCESS,$OT_PROJECT,srcRecord.delete)" in expression " 

java.lang.Exception: Invalid expression xogprojectapi($PROCESS,$OT_PROJECT,srcRecord.delete): 31 

Caused by: java.lang.Exception: 31 
at com.niku.schedulers.api.XOGProjectAPI.returnErrorMessage( 


Release: All
Component: ODBPM


This can happen if you have multiple XOG requests in multiple threads fighting for updates on the same project at the same time. 

Projects get locked during XOG update, so ANY process can lock a Project. Usually it is brief and doesn't cause a problem, but if you have a lot of processes running on the same process instance, this might occasionally happen. 


  1. Revise your use of performing immediate project updates via XOG so that contention doesn’t occur.
  2. Query the prlock table before you do project updates via XOG to avoid the contention. 

    You can run the following query to check if there was a lock on the project or not before you do project updates via XOG to avoid the contention: 

    Select * From PRLOCK where PRRECORDID= the project's internal ID.