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

Migrations taking more time than quarkus.transaction-manager.default-transaction-timeout are not persisted

XMLWordPrintable

    • False
    • None
    • False
    • CR1
    • -
    • Workaround Exists
    • Hide

      Setting quarkus.transaction-manager.default-transaction-timeout long enough, migration works.

      It is expected that transaction cover migration time. In that case (if migration takes too long, this parameter should be adjusted)

      Show
      Setting quarkus.transaction-manager.default-transaction-timeout long enough, migration works. It is expected that transaction cover migration time. In that case (if migration takes too long, this parameter should be adjusted)
    • ---
    • ---
    • 2022 Week 47-49 (from Nov 21)

      Looks like migrations are opening a transaction for the whole migration plan instead of for each process instance migrated. So migration plan taking more than default timeout 60s, fail and do not persist any info about execution (reports)

              rhn-support-rromerom Ruben Romero Montes
              afanjula@redhat.com Alberto Fanjul Alonso
              Gonzalo Muñoz Fernández Gonzalo Muñoz Fernández
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: