Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 7.13.2.GA
Affects Version/s: 7.13.1.GA
Component/s: jBPM Core
Labels:
- bamoe-verified

Blocked:
False
Blocked Reason:
None
Ready:
False
Fix Build:
CR1
QE Test Coverage:
-
Target Release:

7.13.2.GA
Workaround:

Workaround Exists
Workaround Description:

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)
[QE] How to address?:
---
[QE] Why QE missed?:
---

Sprint:
2022 Week 47-49 (from Nov 21)

SFDC Cases Counter:
SFDC Cases Links:

Description

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)

Attachments

Issue Links

links to

7.67.x PR

7.67.x-blue PR

Pull Request

Activity

People

Assignee:: Ruben Romero Montes

Reporter:: Alberto Fanjul Alonso

QA Contact:: Gonzalo Muñoz Fernández

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Dates

Created:: 2022/11/28 8:46 AM

Updated:: 2024/02/12 9:10 AM

Resolved:: 2022/12/09 12:42 PM