Doing a POC with Flowable and Camel. The documentation indicates that you can invoke asynchronously a Camel route from Flowable and have that same Camel Route trigger a Receive Task in the Process that invoked the Camel Route asynchronously.
<serviceTask id="serviceAsyncPing" flowable:type="camel" flowable:async="true"/>
<receiveTask id="receiveAsyncPing" name="Wait State" />
The client, when invoking the process that are configured with these tasks, does come back async but Camel fails when it tries to invoke the “asyncPingProcess” and it appears to be because the serviceAsyncPing never finished. It feels like a catch 22 issue where the process is trying invoke the receive task but the service task never finished. I believe I am reading the docs correctly but the behavior doesn’t work as expected.