You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Jeremy Ross (Jira)" <ji...@apache.org> on 2021/01/26 21:55:00 UTC
[jira] [Created] (CAMEL-16084) salesforce: Out of order execution
Jeremy Ross created CAMEL-16084:
-----------------------------------
Summary: salesforce: Out of order execution
Key: CAMEL-16084
URL: https://issues.apache.org/jira/browse/CAMEL-16084
Project: Camel
Issue Type: Bug
Components: camel-salesforce
Affects Versions: 3.7.1
Reporter: Jeremy Ross
Assignee: Jeremy Ross
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 poolsize, maxsize and queuesize of 1, which should effectively behave in a synchronous manner.
Test case: https://gist.github.com/jeremyross/4d7d14a33452edf236faefda77ad3e3d
--
This message was sent by Atlassian Jira
(v8.3.4#803005)