Are asynchronous user tasks being handled differently since the introduction of the Async executor?

cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Member II

Are asynchronous user tasks being handled differently since the introduction of the Async executor?

Jump to solution

Asynchronous user tasks are being saved in ACT_RU_JOB table and marked with the type "message".

No entry is made in the ACT_RU_TASK table and assigned Users for this User-Task are not able to complete the process.

- Is the Message Queue based Async Executor responsible for this?

If yes, why are asynchronous user tasks handled as jobs ?

In the Activiti User Guider is stated:

16.1.1. Async Executor design

Two types of jobs exist: timers (like those belonging to a boundary event on a user task) and async continuations (belonging to a service task with the activiti:async="true" attribute).

Thanks in advance.

Best regards

Elvi

1 Solution

Accepted Solutions
Highlighted
Senior Member II

Re: Are asynchronous user tasks being handled differently since the introduction of the Async executor?

Jump to solution

User Tasks are not handled by Async Executors. If you don't see them created in the Runtime Task table, it may be a bug. Please create a unit test to reproduce this issue and raise an issue in Activiti project

View solution in original post

2 Replies
Highlighted
Senior Member II

Re: Are asynchronous user tasks being handled differently since the introduction of the Async executor?

Jump to solution

User Tasks are not handled by Async Executors. If you don't see them created in the Runtime Task table, it may be a bug. Please create a unit test to reproduce this issue and raise an issue in Activiti project

View solution in original post

Highlighted
Member II

Re: Are asynchronous user tasks being handled differently since the introduction of the Async executor?

Jump to solution

Thank you Joseph for your answer.

I tested again and noticed a failed configuration of the Job-Executor (it was not started). The User-Task was saved than as expected in the ACT_RU_TASK table.