Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-740

Kie server with PostgreSQL 9.6 fails when its pod is restarted

    XMLWordPrintable

Details

    • CR1
    • Hide
      • Run execution server with PostgreSQL 9.6 using "bpmsuite70-executionserver-externaldb" template
      • Scale number of execution server pods to 0
      • Scale number of execution server pods back to 1
      • Execution server will not be able to correctly connect to the database
      Show
      Run execution server with PostgreSQL 9.6 using "bpmsuite70-executionserver-externaldb" template Scale number of execution server pods to 0 Scale number of execution server pods back to 1 Execution server will not be able to correctly connect to the database

    Description

      KIE server fails when its pod is restarted. Following exception can be found in log:
      org.postgresql.util.PSQLException: ERROR: column am.amcanorder does not exist
      Position: 407

      This bug appears only when Kie server uses PostgreSQL 9.6 database. It works correctly with PostgreSQL 9.3 and MySQL 5.7. Problem is probably caused by old version of PostgreSQL driver in our images: 9.2-1002. See folder: /opt/eap/modules/system/layers/openshift/org/postgresql/main/META-INF/maven

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. RHPAM-181 Kie server timers aren't clustered

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. RHPAM-904 database exception using rhpam70-kieserver-externaldb.yaml when connecting to PostgreSQL

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. RHPAM-785 need to remove the temporary fix for KIE server using postgresql-42.2.2.jar

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBPM-6500 ERROR: column am.amcanorder does not exist

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              czhu_jira calvin zhu (Inactive)
              jpetrlik@redhat.com Jiri Petrlik
              Jiri Petrlik Jiri Petrlik
              Jiri Petrlik Jiri Petrlik
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: