[CAMEL-16084] salesforce: Out of order execution

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Information Provided
• Affects Version/s: 3.7.1
• Fix Version/s: 3.8.0
• Component/s: camel-salesforce
• Estimated Complexity: Unknown
• Assignee: Jeremy Ross
• Reporter: Jeremy Ross
• Created: 26/Jan/21 21:54
• Updated: 29/Mar/21 13:46
• Resolved: 29/Mar/21 13:46

Description

When using a salesforce operation after an aggregator, control seems to return to the aggregate caller immediately instead of proceeding with processors downstream from the salesforce operation. This is the behavior I'd expect if using the aggregator with parallelProcessing.

I believe this is longstanding behavior, however with the removal of the `synchronous` option from the salesforce component (CAMEL-14138), we've removed a workaround to this issue.

I'm seeing the same behavior with a salesforce operation via a wiretap with a threadpool with poolsize, maxsize and queuesize of 1, which should effectively behave in a synchronous manner.

Test case: https://gist.github.com/jeremyross/4d7d14a33452edf236faefda77ad3e3d

Issue Links

• is fixed by: CAMEL-16098 camel-direct - Add synchronous option
• is related to: CAMEL-16106 camel-seda - Endpoints with custom queueSize to create queue lazy
• relates to: CAMEL-16098 camel-direct - Add synchronous option
• relates to: CAMEL-16099 camel-core - Throttler EIP to support max inflight messages without time period