-
Bug
-
Resolution: Fixed
-
Low
-
10.126.3
-
Severity 1 - Critical
-
No
Issue Summary
It was observed during the investigation of the Why field sync (in the connector) that this error is causing a massive number of deadlocks in Jira Align database.
If the parameter "Why? details custom field (text field [multi-line])" on Jira Align is set, then it will trigger the error.
Steps to Reproduce
- Enable the Why field on Jira and in Jira Align
- Update a work item and force the Why field to sync
Expected Results
No deadlocks
Actual Results
It is triggering deadlocks on Jira Align database
{
Exception: System.Data.SqlClient.SqlException (0x80131904): Transaction (Process ID 246) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
Warning: Null value is eliminated by an aggregate or other SET operation.
at Integration.DataAccess.ResilientSqlBase.LogSqlException(ILogger logger, SqlException sqlException)
at Integration.DataAccess.ResilientSqlData.GetDataTable(String connectionString, String sql, SqlParameter[] sqlParameters, Nullable`1 commandTimeout)
at JiraConnector.DataAccess.Repositories.Align.ThemeAlignRepository.GetThemeCompletionPercentByThemeId(Int32 themeId)
at JiraConnector.Services.WhyDetailsBuilderService.BuildFeatureWhy(Int32 featureId)
ClientConnectionId:081769a9-7dd7-43dd-b40a-e592c6242366
Error Number:1205,State:51,Class:13
Level: Error
MessageTemplate: BuildFeatureWhy - Feature ID: XXXXXXX
Properties: {
}
Timestamp: 2024-01-10T14:36:03.7616468+01:00
}
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available