Camel tasks and Concurrency issues

brianok — Tue, 10 Dec 2013 19:06:18 GMT

Hi all,I am using the Camel tasks heavily in a proof of concept for a workflow solution and I have a couple issues that I would like to know if there are best practices in Activiti for overcoming.1. The Apache Camel engine does not seem to deal well with asychronous operations. For example, I have

Re: Camel tasks and Concurrency issues

karl_berger — Mon, 21 Jul 2014 19:47:54 GMT

Sorry to play thread necromancer, but I'm having the exact problem that brianok describes in his first point and would love to know what that workaround looks like.

The User Guide claims that "In starting every camel route, the Process Instance ID will be copied into a camel property with the specific name of "PROCESS_ID_PROPERTY". It is later used for correlating the process instance and camel route. Also it can be exploited in the Camel route. "
But that doesn't seem to be the case in my Activiti->Camel->ActiveMQ integration, or at least it isn't being put to use by Camel. If I try to have an Camel task post to a queue followed by a Receive task, when the Camel route that receives from a "work done" queue and tries to reconnect to my instance I get a "Business Key is null" exception. I looked in the Activiti/Camel code and it only even looks for the Business Key if it doesn't find PROCESS_ID_PROPERTY first.

Help!

topic Re: Camel tasks and Concurrency issues in Alfresco Archive

Camel tasks and Concurrency issues

Re: Camel tasks and Concurrency issues