The Author Online Book Forums are Moving

The Author Online Book Forums will soon redirect to Manning's liveBook and liveVideo. All book forum content will migrate to liveBook's discussion forum and all video forum content will migrate to liveVideo. Log in to liveBook or liveVideo with your Manning credentials to join the discussion!

Thank you for your engagement in the AoF over the years! We look forward to offering you a more enhanced forum experience.

joewei (4) [Avatar] Offline

I'm having a problem with timer boundary events being used in sub process loops.

My sub process is configured to loop subsequently and the first task actually is a receive task where a timer boundary event is being attached to, basically to function as a timeout - so if after a given period of time the receive task hasn't been triggered yet, the sub process will proceed upon the timeout - this is to avoid the sub process hanging endlessly. Another requirement is that the timeout time needs to be configurable and this is calculated within the last task of the sub process.

This all works fine on the very first iteration of the loop, but on all subsequent iterations the receive task doesn't wait to be triggered nor does it wait for the timeout, it just proceeds to the next task right away.

Any idea of what could be the cause for this problem ?

tijs.rademakers (494) [Avatar] Offline
Re: Problem with timer boundary event in sub process loops

When the second iteration is performed, how can the receive task proceed to the next task? What triggers it to go to the next step?
Is it possible to create a unit test of your example so I can test it myself?

Best regards,