Transaction (Process ID ) was deadlocked on lock | communication buffer resources with another process

General
, , ,
1

Error message:

Transaction (Process ID 130) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
DatabaseException caused by prior exception: com.microsoft.sqlserver.jdbc.SQLServerException: Transaction (Process ID 130) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

Above issue happening only in Prod on some of the assignments, no issue if I remove SLA on the assignment.

Also, same issue happening once case resumed on temporary page and routed to wait shape.

No issues observed in logs, above error message is from broekn queue items "System-Queue-ServiceLevel ".

Can please help to check this.

2

@Lee Krish The error message indicates a deadlock situation in the database related to SLAs and wait shapes. Ensure consistent lock request order in custom code, consult with your DBA for performance issues, and consider applying specific DSS settings to handle batch updates and merge statements.

:warning: This is a GenAI-powered tool. All generated answers require validation against the provided references.

Case Status is displayed as “Error: Exception”. Why?

Keep seeing deadlock on Log-RuleUsage-Details - why and what is the impact

Getting deadlock on lock resources

3

@MarijeSchillern

Standard workflow for the application, and to add got many Applications in the same instance and only one Application affected with this issue. Can anyone help to check. Thanks.

4

@Lee Krish if you need this to be investigated as a product issue please log a support incident via the MSP and provide the INC id here so that we can help track it.

5

@MarijeSchillern

Raised SR INC-B32523 and pending from long time.

6

@Lee Krish Thanks, I can see that INC-B32523 was opened the day after you posted this question on the forum.

Our GCS team are investigating your ticket and you have had some webex sessions to look into the issue. Please continue to work with them.

I will let them know that you have provided an update in the ticket.

7

@Lee Krish

·
INC-B32523 has been resolved with the below:

Solution type description:

Addressed issues related to URL mapping and opening cases in the PPF view, with plans to resolve these problems:

Findings : The issue is inconsistent and is not reproducible in lower environments. The client has configured an SLA rule on assignment. Sometimes,
the SLA items goes to broken queue with the error message, Transaction was deadlock on lock. Also, when the assignments are processed by a file listener,
the case goes through a wait shape and when it resumes, it goes to broken queue with same error message. When the SLA is removed from assignment, it works fine.
Suggested few steps for the client to take care.

Error :
OutputPageName=;*[MSG][Error in commit()][STACK][com.pega.pegarules.pub.database.DatabaseException:
Transaction (Process ID 142) was deadlocked on lock resources with another process and has been chosen as the
deadlock victim. Rerun the transaction.DatabaseException caused by prior exception:
com.microsoft.sqlserver.jdbc.SQLServerException: Transaction (Process ID 142)
was deadlocked on lock resources with another process and has been chosen as the deadlock victim

This is a clear design issue without completing the file listener transaction. The wait shape transaction has been started and tried to commit the case data, leading to the problem

Instead of wait , replace it with an assignment. Set the goal time dynamically and avoid the deadline transaction.