[
https://issues.apache.org/jira/browse/CAMEL-12712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625854#comment-16625854
]
Jesse Sightler commented on CAMEL-12712:
----------------------------------------
TBH, even if it is the test services there is a serious issue here. Switching
to seda completely changes the behavior in a way that shouldn't be possible.
The services work fine as long as the client doesn't block the response thread.
> Camel Salesforce can easily hang when used within an aggregator
> ---------------------------------------------------------------
>
> Key: CAMEL-12712
> URL: https://issues.apache.org/jira/browse/CAMEL-12712
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
> Reporter: Jesse Sightler
> Priority: Major
>
> Reproducer project:
> https://github.com/jsight/camel-salesforce-http-aggregator-issue
>
> Run the unit tests and you will observe it hanging.
>
> A workaround is also present. Uncomment this line:
> {quote}// .to("seda:enrichWithJobId?waitForTaskToComplete=Always")
> {quote}
>
> The code that hangs is this:
> {quote}.enrich("direct:createJobAndGetID", new AggregationStrategy() {
> @Override
> public Exchange aggregate(Exchange oldExchange, Exchange newExchange)
> Unknown macro: \{ oldExchange.getIn().setHeader("jobId",
> newExchange.getIn().getBody(JobInfo.class).getId()); return oldExchange; }
> })
> {quote}
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
