JBoss 7.1.x - standalone-ha mode.
Flowable - 6.4.0
ActiveMQ - for service task/long-running task
Design wise, most of the BPMN activities are defined as async and exclusive.
Behavior/Identified Issues during peak hour:
found the async job executor race condition higher, it creates issues like,
- Task creation/execution duplicated more than twice
- Call activity/ Service Task/SubProcesses skipped - Some subprocess will skip and it will go to the next step in the process
- Keeping Job executor active only in one node. eg.
Node 1 - flowable-async-executor-activate=true
Node 2 - flowable-async-executor-activate=false
- long term solution could be: move Async operation to JMS queue (https://www.flowable.org/docs/userguide/index.html#_message_queue_based_async_executor)
Please share your suggestions!!