[
https://issues.apache.org/jira/browse/CAMEL-16877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401834#comment-17401834
]
Jeremy Ross commented on CAMEL-16877:
-------------------------------------
This feels similar to this https://issues.apache.org/jira/browse/CAMEL-14138.
Workaround is going back to camel 3.7.x, in which the salesforce component
still has the synchronous option and always using synchronous=true.
I suspect that in route1 the operation is async, then because route2 is
transacted, it's forced to be sync, then the deadlock happens.
> camel-salesforce: any salesforce operation inside transaction times out
> -----------------------------------------------------------------------
>
> Key: CAMEL-16877
> URL: https://issues.apache.org/jira/browse/CAMEL-16877
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
> Affects Versions: 3.11.1
> Reporter: Jeremy Ross
> Priority: Major
>
> A transacted route with a salesforce operation will time out if it's called
> from a non-transacted route with a salesforce operation.
> Reproducer here:
> https://github.com/jeremyross/camel-transacted-salesforce-reproducer
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
