[ https://issues.apache.org/jira/browse/CAMEL-12712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16578278#comment-16578278 ]
Jesse Sightler commented on CAMEL-12712: ---------------------------------------- Did you uncomment the call to the seda and comment out the ".enrich("direct:createJobAndGetID", new AggregationStrategy() {" block? It will not block if you do that. I can share a video to make this clear if you'd like? I'm not convinced that the http stack would crash in the same way with a mock or that the code would be vastly simpler with Wiremock. > 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)