Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-5564

PostgreSQL healtcheck fails when reactive client is used

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 1.10.0.Final
    • 1.9.0.Final
    • Core Engine
    • None
    • False
    • False
    • Undefined
    • Hide

      Start process-postgresql-persistence-quarkus example with Maven command:
      mvn compile quarkus:dev -Ppersistence

      Open the page/ send a GET request to http://localhost:8080/q/health

      Check console log.

      Show
      Start process-postgresql-persistence-quarkus example with Maven command: mvn compile quarkus:dev -Ppersistence Open the page/ send a GET request to http://localhost:8080/q/health Check console log.
    • 2021 Week 28-30 (from Jul 12), 2021 Week 31-33 (from Aug 2)

      When PostgreSQL reactive client is used in Kogito application, then healtcheck fails with error listed in attachment.

      Seems to affect just Quarkus.

      Readyness status

      {
    "status": "DOWN",
    "checks": [
        {
            "name": "io.quarkus.reactive.pg.client.runtime.health.ReactivePgDataSourcesHealthCheck_ClientProxy",
            "status": "DOWN",
            "data": {
                "rootCause": "Running in a Vertx context => use PgPool#pool(Vertx, PgConnectOptions, PoolOptions) instead"
            }
        }
    ]

        1. stacktrace.txt
          7 kB

              cnicolai@redhat.com Cristiano Nicolai (Inactive)
              ksuta Karel Suta
              Marian Macik Marian Macik
              Marian Macik Marian Macik
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: