Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-6497

BuildFeatureWhy triggering deadlocks on Jira Align database


    • 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

      1. Enable the Why field on Jira and in Jira Align
      2. 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)
      Error Number:1205,State:51,Class:13
         Level: Error
         MessageTemplate: BuildFeatureWhy - Feature ID: XXXXXXX
         Properties: { 
         Timestamp: 2024-01-10T14:36:03.7616468+01:00


      Currently, there is no known workaround for this behavior. A workaround will be added here when available

            fea1a6ef3355 Yannick Genin
            f9fc804f30c6 Luiz Felipe Arruda
            0 Vote for this issue
            6 Start watching this issue