[
https://issues.apache.org/jira/browse/CAMEL-22332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18013765#comment-18013765
]
Claus Ibsen commented on CAMEL-22332:
-------------------------------------
Thanks we could consider having some worker pool for salesforce so the received
events are routed by another thread. However this may lead to the consumer
thread being able to pickup new messages while the worker pool is still
processing the previous message; leading to out of ordering etc. Or we add a
note in the docs and people can use wiretap if they have a need as you do.
> Salesforce API Calls Hang During PushTopic Event Processing
> -----------------------------------------------------------
>
> Key: CAMEL-22332
> URL: https://issues.apache.org/jira/browse/CAMEL-22332
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
> Affects Versions: 4.13.0
> Reporter: Aldon Utley
> Priority: Minor
> Fix For: 4.x
>
> Attachments: example.zip
>
>
> I ran in to this issue when updating an app from Camel 2.X to 4.13.
> The Salesforce calls work as expected unless they are invoked during the
> processing of a Salesforce PushTopic event, in which case, they hang
> indefinately.
> In my example application, I've added the same Saleforce API calls to the
> afterApplicationStart() mehtod of the CamelContext and to a bean processing a
> PushTopic event.
> Steps to reproduce:
> 1. Select a Salesforce Account to use for testing.
> 2. Update the id and email values in the CamelConfiguration class with
> values from the test Account.
> 3. Start the application and observe that the initial Salesforce API
> calls to fetch account data succeed.
> 4. Trigger a PushTopic event by modifying the name of your test Account
> in Salesforce.
> 5. Observe that the application hangs when attempting to execute a
> Salesforce API call from within the PushTopic event listener.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
