Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

Kaleo Fork Causes Microsoft SQL Server Deadlock

Written By

Michael Warren Young

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • When using Microsoft SQL Server as Liferay's database, using a workflow with a fork will cause the database server to deadlock

Environment

  • Liferay Portal or Liferay DXP with Microsoft SQL Server as Liferay's database

Resolution

  • When using SQL Server as Liferay's database, the Read Committed Snapshot Isolation level must be manually enabled.
  • This Support Policy article details this:

    For SQL Server to function properly with the product, SQL Server’s Read Committed Snapshot Isolation level must be turned on. While other databases enable this behavior out of the box, it is disabled by default for SQL Server.

Additional Information

  • Please review the following articles from Microsoft regarding Database Snapshots in SQL Server:

1) https://technet.microsoft.com/en-us/library/ms189940(v=sql.105).aspx
2) https://technet.microsoft.com/en-us/library/ms175095(v=sql.105).aspx

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?