Vulnerability in EPiServer.Forms
Here's a simple KQL query you can run in AI Logs to summarize exceptions from the Azure SQL calls:
| where target contains ".database.windows.net"
| where tostring(customDimensions.Exception) !contains "Violation of"
| summarize sum(itemCount) by substring(tostring(customDimensions.Exception),0,275)
| order by sum_itemCount desc
| project sum_itemCount, Column1
Looking into stability issues and when problems arise we see large amounts of these:
I'm interested if others are also seeing these two exceptions in some volume for their CMS 12 on DXP?
Here's an issue for SqlClient that suggests this may be a broader issue with dotnet core running in Linux containers in general:https://github.com/dotnet/SqlClient/issues/1530 For the DXP this suggests some tweaks are already in place:https://support.optimizely.com/hc/en-us/articles/4432366206733-CMS-12-site-crash-due-to-SQL-timeout-error-when-working-in-CMS-edit-mode
A shot in the dark but maybe this is with MARS enabled? When I was testing performance for CMS 12 MARS does not work well on Linux
Hi Johan, did you manage to resolve these errors? We're receiving the same error in DXP 😞
Microsoft.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired.
The timeout period elapsed prior to completion of the operation or the server is not responding.
Operation cancelled by user.
The statement has been terminated.
System.ComponentModel.Win32Exception (258): Unknown error 258
We still see them and usually at high volume in proximity of reported downtime. But there can also be tens of millions operations between showings.
Here is another issue with the client package that we are following since we usually see the problem around queries that are doing heavier work. Unfortunately they are not our own queries but if they were this issue thread suggest re-working those calls to be sync and not async.