-
Task
-
Resolution: Done
-
Major
-
1.10.0.Final
-
None
-
False
-
False
-
-
2021 Week 37-39 (from Sep 13), 2021 Week 40-42 (from Oct 4), 2021 Week 43-45 (from Oct 25), 2021 Week 46-48 (from Nov 15)
Currently there is no async execution, if the async property is set to true in the editor, the property is not even considered in the runtimes.
Implement the async execution for nodes that allow the async property to be set.
Update:
The async execution behavior should use job-service to control the trigger of async nodes execution, in this way we have out of the box, retries, failures, status control offered by job-service and mainly persisted in the database.
Using an executor service, in memory to execute in different threads has the downside to loose information of execution in case of failures, service restart, etc.
- incorporates
-
KOGITO-5733 "Parallel" multiple instance execution is not parallel
- Closed
- is duplicated by
-
KOGITO-6128 Persistence is not working with embedded collections
- Closed
- is related to
-
KOGITO-6093 JandexProtoGenerator NPE when generating process with variable of type List
- Closed
- relates to
-
KOGITO-4661 Multiple Instance Sub-Proces
- Closed
-
KOGITO-5488 null pointer exception when building very simple processes with multiple instance subprocess
- Closed
-
KOGITO-5467 Error while marshalling process instance (multiple instance ArrayList)
- Closed
-
KOGITO-5733 "Parallel" multiple instance execution is not parallel
- Closed