Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

SQL Server Database May Lock When Publishing Content in a Staged Environment or Importing a LAR

Written By

Liferay Support

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.

Liferay portal may appear to hang or be unresponsive when importing a LAR or publishing to staging. This occurs if the database used in your environment is a SQL Server with default transaction isolation settings and it occurs regardless of the size of the content.

Resolution

1. Set in portal-ext.properties:

jdbc.default.liferay.pool.provider=dbcp
jdbc.default.defaultTransactionIsolation=READ_COMMITTED

2. Run queries:

ALTER DATABASE lportal SET ALLOW_SNAPSHOT_ISOLATION ON;
ALTER DATABASE lportal SET READ_COMMITTED_SNAPSHOT ON;
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?