Stefan
August 2, 2021, 7:48am
1
Hi,
joram
August 2, 2021, 1:08pm
2
Due to a massive amount of work this year (which is a good thing from a certain angle
Stefan
August 2, 2021, 2:05pm
3
Thanks for the quick reply.
We currently have a couple of open contributions as Pull Requests:
flowable:master ← sap-contributions:fix-async-mi-waitstate
opened 05:58PM - 24 Feb 21 UTC
Without this change a flow node with multi-instance characteristics marked as as… ynchronous is still initially executed synchronously by the ContinueProcessOperation. If a failure happens during the initialization of the multi-instance, e.g. the referenced collection does not exist, then a rollback occurs. However, this rollback disregards that the asynchronous flow node should be a wait state and instead rolls back to the beginning of any previous asynchronous activity.
Example: Start Event --> Async Script Task --> Async Multi-Instance Call Activity --> End Event
If the multi-instance call activity fails because the collection variable cannot be resolved, then the execution is rolled back all the way to before the script task, whereas the expectation would be that the execution is rolled back only to the beginning of the call activity, because it is marked as asynchronous.
This change fixes this by removing the special case for multi-instance activities in ContinueProcessOperation, so that any asynchronous flow node again first commits the transaction and creates a new async-continuation job and is then actually being executed when it is later picked up by the job executor.
#### Check List:
* Unit tests: YES (MultiInstanceTest::testAsync**Rollback)
* Documentation: NA
flowable:master ← tinabandaloemruli:ConcurrentHashMaps_SharedExecutorServiceAsyncExecutor
opened 08:40AM - 31 Mar 21 UTC
#### Check List:
* Unit tests: YES
* Documentation: No
changed Maps to Con… currentHashMaps for SharedExecutorServiceAsyncExecutor
flowable:master ← sap-contributions:cleanup-callactivitybehavior
opened 11:59AM - 18 Dec 20 UTC
* Declare "variables" HashMap inline to avoid it being accidentally used further… down
* Use already retrieved eventDispatcher instead of fetching it again from process engine configuration
#### Check List:
* Unit tests: NA
* Documentation: NA
Do you see chances that they will make it ino the 6.7.0 release? Even if it gets delayed
), we’ve had to postpone it a few times. Right now our goal is to release it this month - but no promises.