Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-40754

Information regarding use of validation-query-timeout is not consistent.

      NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.

      In Tuning Database Connections it states "If you specify a Validation Query above, then you should specify a value for the Validation Query Timeout too."

      However, in Surviving Connection Closures it says " This should only be done for MySQL" and " If the Validation Query Timeout is used on any database other than MySQL it will cause significant problems with the JIRA instance."

      Which is truthier? The other should be updated to match.

      Cheers,
      Morg.

            [JRASERVER-40754] Information regarding use of validation-query-timeout is not consistent.

            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2841837 ] New: JAC Bug Workflow v3 [ 2909822 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2579805 ] New: JAC Bug Workflow v2 [ 2841837 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1539090 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2579805 ]
            jonah (Inactive) made changes -
            Description Original: In [Tuning Database Connections|https://confluence.atlassian.com/display/JIRA/Tuning+Database+Connections#TuningDatabaseConnections-settings] it states "If you specify a Validation Query above, then you should specify a value for the Validation Query Timeout too."

            However, in [Surviving Connection Closures|https://confluence.atlassian.com/display/JIRA/Surviving+Connection+Closures] it says "(!) This should only be done for MySQL" and "(!) If the Validation Query Timeout is used on any database other than MySQL it will cause significant problems with the JIRA instance."

            Which is truthier? The other should be updated to match.

            Cheers,
            Morg.
            New: {panel:bgColor=#e7f4fa}
              *NOTE:* This bug report is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JRACLOUD-40754].
              {panel}

            In [Tuning Database Connections|https://confluence.atlassian.com/display/JIRA/Tuning+Database+Connections#TuningDatabaseConnections-settings] it states "If you specify a Validation Query above, then you should specify a value for the Validation Query Timeout too."

            However, in [Surviving Connection Closures|https://confluence.atlassian.com/display/JIRA/Surviving+Connection+Closures] it says "(!) This should only be done for MySQL" and "(!) If the Validation Query Timeout is used on any database other than MySQL it will cause significant problems with the JIRA instance."

            Which is truthier? The other should be updated to match.

            Cheers,
            Morg.
            jonah (Inactive) made changes -
            Link New: This issue relates to JRACLOUD-40754 [ JRACLOUD-40754 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 759459 ] New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1539090 ]
            Wazza made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]
            Andrew made changes -
            Sprint New: Sprint 11 [ 3023 ]
            Wazza made changes -
            Story Points New: 4
            Wazza made changes -
            Rank New: Ranked higher

              wthompson Wazza
              mknicely Morgan Knicely (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: