Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-16084

salesforce: Out of order execution

    XMLWordPrintableJSON

    Details

    • 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
    • Labels:
      None
    • Estimated Complexity:
      Unknown

      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

        Attachments

        1. wiretap-results.txt
          17 kB
          Jeremy Ross

          Issue Links

            Activity

              People

              • Assignee:
                jeremyross Jeremy Ross
                Reporter:
                jeremyross Jeremy Ross
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: