This article refers to legacy products, components or features. Therefore, the content in this article is offered "as is" and will no longer be updated. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.
When running K2 processes on a single server or clustered environment, certain process instances may cause deadlocks within the K2 Server when running under high load.
This issue may be caused by the following circumstances:
- There are a large amount of data within the K2 Server.
- There are high volumes of read and write tasks taking place within one process instance, or multiple processes on the same K2 Server or clustered environment.
The following error is known to occur:
1 Transaction (Process ID 63) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
This Hotfix is contained within the latest K2 Update. Install the update package to resolve the error.