Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-15548

[Fuse Online] Export integrations leaves opened connections to the syndesis-db

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • fuse-7.9-GA
    • fuse-7.8-GA
    • Fuse Online
    • None
    • False
    • False
    • % %
    • ?
    • Undefined
    • Hide
      • oc rsh in syndesis-db pod
      • watch -n .1 'ps auxww|grep "syndesis (10.2.1.1" '
      • from Fuse online ui create a new environment and marked one integration
      • perform a manual export with a curl from bash like
        curl -location --request GET 'https://syndesis-public/api/v1/public/integrations/t1/export.zip' --header 'Content-Type: application/json' --header 'SYNDESIS-XSRF-TOKEN: awesome' --header 'Authorization: Bearer <TOKEN>' --noproxy "*" -kv -o test.zip

      After this we seen that in syndesis-db pod appeared a new connection and it remains like:
      1000330+ 31876 1.6 0.1 1218440 107028 ? Ss 12:05 0:01 postgres: syndesis syndesis 10.2.1.1(56680) idle in transaction

      Show
      oc rsh in syndesis-db pod watch -n .1 'ps auxww|grep "syndesis (10.2.1.1" ' from Fuse online ui create a new environment and marked one integration perform a manual export with a curl from bash like curl - location --request GET 'https://syndesis-public /api/v1/public/integrations/t1/export.zip' --header 'Content-Type: application/json' --header 'SYNDESIS-XSRF-TOKEN: awesome' --header 'Authorization: Bearer <TOKEN>' --noproxy "*" -kv -o test.zip After this we seen that in syndesis-db pod appeared a new connection and it remains like: 1000330+ 31876 1.6 0.1 1218440 107028 ? Ss 12:05 0:01 postgres: syndesis syndesis 10.2.1.1(56680) idle in transaction

    Description

      the export process using public API is leaving opened connections:

      curl --location --request GET 'https://syndesis-public-/api/v1/public/integrations/t1/export.zip' --header 'Content-Type: application/json' --header 'SYNDESIS-XSRF-TOKEN: awesome' --header 'Authorization: Bearer <TOKEN>' --noproxy "*" -kv -o test.zip

      ends with a new connection and it remains like:

      1000330+  31876  1.6  0.1 1218440 107028 ?      Ss   12:05   0:01 postgres: syndesis syndesis 10.2.1.1(56680) idle in transaction:

      The syndesis-server logs shows the following exception:

      Internal Server Exception. java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 30000ms.

      Attachments

        Activity

          People

            zregvart@redhat.com Zoran Regvart
            rhn-support-aboucham Abel Bouchama
            Matej Kralik Matej Kralik
            Votes:
            2 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: