Question & Answer
Question
What are OptimisticLockException messages in the client.log?
Caused by: com.co3.web.exception.MappableExceptionImpl: javax.persistence.OptimisticLockException: Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1;
Answer
OptimisticLockException messages are generally caused by multiple requests trying to update the same data at the same time. The system automatically retries those requests. So most of the time there is no user or functional impact.
Often, at the time of the message the client.log will show an API call detailing the endpoint, task, incident that is being updated. There might also be SQL output providing more insight as to what is running at the same time.
Often this is caused by integrations running at the same time and can be resolved by assessing the triggers of such integrations such as rules and workflows.
[{"Line of Business":{"code":"LOB24","label":"Security Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSIP9Q","label":"IBM Security SOAR"},"ARM Category":[{"code":"a8m0z000000cwJqAAI","label":"Resilient Core->Debugging"}],"ARM Case Number":"TS004200790","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]
Was this topic helpful?
Document Information
Modified date:
19 April 2021
UID
ibm16333611