Summary

      Ranking operations are taking a huge delay in Microsoft SQL 2012, when executed in huge instances (reproduced in an instance with more than 1.500.000 issues).
      Due to the delay, the ranking operation times out and fails very frequently. The message below is displayed in the UI:
      "JIRA Agile cannot execute the rank operation at this time. Other users may be ranking the issues that you are trying to rank. Please try again later"

      Environment

      • Tested with Microsoft SQL 2008 and 2012
      • JIRA Agile 6.6.80
      • 1.500.000 issues

      Steps to Reproduce

      1. In a JIRA Instance connected with MSSQL, generate at least 1.000.000 issues
      2. Create a test board and add some hundred of issues to its backlog
      3. Try to rank the issues
      4. This can be reproduced by either ranking a single issue, or ranking multiple issues at the same time

      Expected Results

      The issues should be ranked successfully

      Actual Results

      The following error will be thrown:

      Sometimes it appears that the operation worked, but after refreshing the page the issues are back to their original position in the backlog.

      Workaround

      When affected by this issue, there is one change that have to be implemented to actually workaround this problem:

      1 - Add sendStringParametersAsUnicode=false to the JDBC connection string
      1. Open the $JIRA_HOME/dbconfig.xml file
      2. Append the following option the connection string ;sendStringParametersAsUnicode=false to the jdbc-datasource/url tag value
        • Connection string will look like the following (url might have extra parameters at the end):
          jdbc:jtds:sqlserver://<SERVER_URL>:<SERVER_PORT>/<DB_NAME>;sendStringParametersAsUnicode=false
          
      3. Restart JIRA

            [JSWSERVER-12221] JIRA Agile performs slowly when using Microsoft SQL Server

            Oleksandr Tkachenko made changes -
            Remote Link Original: This issue links to "JSEV-121 (JIRA Server)" [ 170248 ] New: This issue links to "JSEV-121 (JIRA Server (Bulldog))" [ 170248 ]
            Bugfix Automation Bot made changes -
            Minimum Version New: 6.06
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2856027 ] New: JAC Bug Workflow v3 [ 2937986 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545583 ] New: JAC Bug Workflow v2 [ 2856027 ]

            asfsdafsad

            i1049919 i1049919 added a comment - asfsdafsad

            April added a comment -

            Please take a look at my comment on JSWSERVER-15917.

            This is not resolved, due to wrong data type is being declared for Quartz tables in in fieldtype-mssql.xml under \WEB-INF\classes\entitydefs

            April added a comment - Please take a look at my comment on  JSWSERVER-15917 . This is not resolved, due to wrong data type is being declared for Quartz tables in in fieldtype-mssql.xml under \WEB-INF\classes\entitydefs
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1548378 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545583 ]
            Andriy Yakovlev [Atlassian] made changes -
            Link New: This issue relates to JSWSERVER-15917 [ JSWSERVER-15917 ]
            Vinicius Fontes made changes -
            Affects Version/s New: 7.2.8 Server [ 66025 ]

            Please reopen this bug,as this isssue is happening in 7.2.7

            Honeywell JIRA Admin added a comment - Please reopen this bug,as this isssue is happening in 7.2.7

              Unassigned Unassigned
              psouza Pedro Souza
              Affected customers:
              4 This affects my team
              Watchers:
              14 Start watching this issue

                Created:
                Updated:
                Resolved: