[
https://issues.apache.org/jira/browse/CAMEL-12712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16573269#comment-16573269
]
Zoran Regvart commented on CAMEL-12712:
---------------------------------------
[[email protected]] if you run the test through a debugger you'll notice
that the HTTP response is never received for the
{{/services/async/37.0/job/\{jobid\}/batch}} request -- this causes the
exchange never to complete. Try setting a breakpoint in {{onResponse}} in the
inner class extending {{ClientResponseCallback}} created in
{{org.apache.camel.component.salesforce.internal.client.DefaultBulkApiClient::createJob}}
or running with Jetty DEBUG logging
{{-Dorg.eclipse.jetty.util.log.class=org.eclipse.jetty.util.log.StdErrLog
-Dorg.eclipse.jetty.LEVEL=DEBUG}}.
> 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)
