Timeout firing after execution leaves sub-process?

[blezek]

Hi,

  Please see the attached diagram.

I have a workflow that uses a subprocess.  The subprocess waits for a set of series to arrive (labeled #1, see the associated question), when everything is ready, the workflow should proceed to the plugin (a JavaDelegate, labeled #3).  But the plugin takes longer than the sub-process timeout (labeled #2) and the workflow exits (labeled #4) through the timeout branch, not the "plugin" branch.

If the "plugin" is async, all works well, but if not, the sub-process timeout fires and the workflow exits unexpectedly.  I would not have expected this behavior.

Should Activiti detect that the execution has left the sub-process and cancel the timeout?

Thanks,

-dan

[daisuke-yoshimo]

Why is it inconvenient if it is asynchronous?

If it is synchronous, since the transaction is not committed until Recieve task is arreived, the timer job cannot check that the subprocess has completed.