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

Upgrade PostgresSQL JDBC driver to 42.2.16+ version

XMLWordPrintable

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Problem Definition

      Jira 8.13.x has PostgresSQL driver version 42.2.6. This version has a bug regarding socketTimeout parameter (see https://github.com/pgjdbc/pgjdbc/pull/1831)

      This is fixed in Version 42.2.15 (2020-08-14). Please search for 'Make sure socketTimeout is enforced PR 1831 210b27a6' at https://jdbc.postgresql.org/documentation/changelog.html#version_42.2.0

      Suggested Solution

      Upgrade bundled PostgresSQL JDBC driver to 42.2.16+ version

      Note on fix

      Staring from Jira 8.16.0 we introduced additional PostgresJdbcConnectionHealthCheck which suggests adding "tcpKeepAlive=true and socketTimeout" parameters and generates the warning in case they are not present:
      "We've detected that your Jira instance is not using optimal PostgreSQL JDBC configuration"

      See related KB: Connection problems to PostgreSQL result in stuck threads in Jira

      Workaround

      Upgrade driver manually

            [JRASERVER-71982] Upgrade PostgresSQL JDBC driver to 42.2.16+ version

            Andriy Yakovlev [Atlassian] added a comment -

            Folks,

            I've created a new ticket to track GSSEncMode problem, please check JRASERVER-72629.

            Thanks.

            Andriy Yakovlev [Atlassian] added a comment - Folks, I've created a new ticket to track GSSEncMode problem, please check JRASERVER-72629 . Thanks.

            Valiantys Support added a comment -

            https://jira.atlassian.com/browse/CONFSERVER-60515?error=login_required&error_description=Login+required&state=21dcf925-3c6c-443d-b68e-9e2479bcc55c

            This was picked up in Confluence, yet Jira is stuck with 42.2.16

            Why not upgrade to latest, test and support with that version?

            Valiantys Support added a comment - https://jira.atlassian.com/browse/CONFSERVER-60515?error=login_required&error_description=Login+required&state=21dcf925-3c6c-443d-b68e-9e2479bcc55c This was picked up in Confluence, yet Jira is stuck with 42.2.16 Why not upgrade to latest, test and support with that version?

            Gonchik Tsymzhitov added a comment -

            Looks like better to set 42.2.19+

            Because we met with next logs:

            < 2021-06-21 14:17:41.854 MSK > FATAL: unsupported frontend protocol 1234.5680: server supports 2.0 to 3.0
< 2021-06-21 14:17:41.863 MSK > FATAL: unsupported frontend protocol 1234.5680: server supports 2.0 to 3.0
< 2021-06-21 14:17:41.870 MSK > FATAL: unsupported frontend protocol 1234.5680: server supports 2.0 to 3.0

            GSSEncMode affected us as I see

            Gonchik Tsymzhitov added a comment - Looks like better to set 42.2.19+ Because we met with next logs: < 2021-06-21 14:17:41.854 MSK > FATAL: unsupported frontend protocol 1234.5680: server supports 2.0 to 3.0 < 2021-06-21 14:17:41.863 MSK > FATAL: unsupported frontend protocol 1234.5680: server supports 2.0 to 3.0 < 2021-06-21 14:17:41.870 MSK > FATAL: unsupported frontend protocol 1234.5680: server supports 2.0 to 3.0 GSSEncMode affected us as I see

              Unassigned Unassigned
              ayakovlev@atlassian.com Andriy Yakovlev [Atlassian]
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: