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

          Form Name

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

            Andriy Yakovlev [Atlassian] made changes -
            Link New: This issue relates to SAMLDC-95 [ SAMLDC-95 ]
            Andriy Yakovlev [Atlassian] made changes -
            Link New: This issue was cloned as JRASERVER-72629 [ JRASERVER-72629 ]
            Andriy Yakovlev [Atlassian] made changes -
            Description Original: h3. 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

            h3. Suggested Solution
            Upgrade bundled PostgresSQL JDBC driver to *42.2.16+* version

            h3. 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|https://confluence.atlassian.com/jirakb/connection-problems-to-postgresql-result-in-stuck-threads-in-jira-1047534091.html]
             
            h3. Workaround
            Upgrade driver manually             		New: h3. 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

            h3. Suggested Solution
            Upgrade bundled PostgresSQL JDBC driver to *42.2.16+* version

            h3. 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|https://confluence.atlassian.com/jirakb/connection-problems-to-postgresql-result-in-stuck-threads-in-jira-1047534091.html]
             
            h3. Workaround
            Upgrade driver manually
            Andriy Yakovlev [Atlassian] made changes -
            Description Original: h3. 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

            h3. Suggested Solution
            Upgrade bundled PostgresSQL JDBC driver to *42.2.16+* version

            h3. 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|https://confluence.atlassian.com/jirakb/connection-problems-to-postgresql-result-in-stuck-threads-in-jira-1047534091.html]
             
            h3. Workaround
            Upgrade driver manually             		New: h3. 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

            h3. Suggested Solution
            Upgrade bundled PostgresSQL JDBC driver to *42.2.16+* version

            h3. 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|https://confluence.atlassian.com/jirakb/connection-problems-to-postgresql-result-in-stuck-threads-in-jira-1047534091.html]
             
            h3. Workaround
            Upgrade driver manually
            Andriy Yakovlev [Atlassian] made changes -
            Description Original: h3. 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

            h3. Suggested Solution
            Upgrade bundled PostgresSQL JDBC driver to *42.2.16+* version
             
            h3. Workaround
            Upgrade driver manually             		New: h3. 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

            h3. Suggested Solution
            Upgrade bundled PostgresSQL JDBC driver to *42.2.16+* version

            h3. 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|https://confluence.atlassian.com/jirakb/connection-problems-to-postgresql-result-in-stuck-threads-in-jira-1047534091.html]
             
            h3. Workaround
            Upgrade driver manually
            Andriy Yakovlev [Atlassian] made changes -
            Fix Version/s New: 8.13.6 [ 94800 ]
            Fix Version/s New: 8.16.0 [ 94594 ]
            Resolution New: Fixed [ 1 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]
            Andriy Yakovlev [Atlassian] made changes -
            Summary Original: Upgrade PostgresSQL JDBC driver to 42.2.26+ version New: Upgrade PostgresSQL JDBC driver to 42.2.16+ version
            Andriy Yakovlev [Atlassian] made changes -
            Description Original: h3. 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

            h3. Suggested Solution
            Upgrade bundled PostgresSQL JDBC driver to *42.2.26+* version
             
            h3. Workaround
            Upgrade driver manually             		New: h3. 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

            h3. Suggested Solution
            Upgrade bundled PostgresSQL JDBC driver to *42.2.16+* version
             
            h3. Workaround
            Upgrade driver manually
            Andriy Yakovlev [Atlassian] made changes -
            Labels New: database pse-request
            Andriy Yakovlev [Atlassian] made changes -
            Description Original: h3. 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

            h3. Suggested Solution
            Upgrade bundled PostgresSQL JDBC driver to 42.2.26+ version
             
            h3. Workaround
            Upgrade driver manually             		New: h3. 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

            h3. Suggested Solution
            Upgrade bundled PostgresSQL JDBC driver to *42.2.26+* version
             
            h3. Workaround
            Upgrade driver manually

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

                Created:
                Updated:
                Resolved: