We're currently experiencing sporadic (once per 1 or 2 weeks) SQL Timeouts on an Umbraco 10.4.2 website. This causes most of the functionality of the BackOffice to fail (the website itself functions, but it is most likely due to caching). There is still an active connection with the database and logging into the Umbraco BackOffice is still possible, but loading any tree causes SQL Timeout exceptions.
The last time we encountered this issue we discovered that the following query was among the "Active Expensive Queries" in SQL Management Studio:
SELECT value FROM umbracoLock WITH (REPEATABLEREAD) WHERE id=@0
Going directly to the database server and querying to the table results in waiting indefinitely. This likely seems to be the cause of the issue.
Because the logic that executes this query is called so often and by a broad collection of functionality it is very difficult to pinpoint exactly what is going wrong. But maybe anyone can give me pointers to what can cause this table to become unresponsive (and what could likely be the case).
SQL Timeouts caused by UmbracoLock table not responding
Hi there!
We're currently experiencing sporadic (once per 1 or 2 weeks) SQL Timeouts on an Umbraco 10.4.2 website. This causes most of the functionality of the BackOffice to fail (the website itself functions, but it is most likely due to caching). There is still an active connection with the database and logging into the Umbraco BackOffice is still possible, but loading any tree causes SQL Timeout exceptions.
The last time we encountered this issue we discovered that the following query was among the "Active Expensive Queries" in SQL Management Studio:
Going directly to the database server and querying to the table results in waiting indefinitely. This likely seems to be the cause of the issue.
Because the logic that executes this query is called so often and by a broad collection of functionality it is very difficult to pinpoint exactly what is going wrong. But maybe anyone can give me pointers to what can cause this table to become unresponsive (and what could likely be the case).
Help is greatly appreciated!
Dennis
is working on a reply...