Hi Daniel, Were you able to resolve this issue? There are no known connection blocking issues in Salesforce, so I am not sure what could be causing your sample scenario to block after the first message.
On Monday, January 19, 2015 10:36 AM, Daniel Pocock <dan...@pocock.pro> wrote: I've tried to make a route that does a Salesforce query and then uses a value from the result for creating an object in Salesforce. JMS message ---> enrich ---> to("salesforce:createSObject"); ^ ^ ^ salesforce:query After starting the application, it works fine for the first message on the queue but after that nothing happens. Is there any potential issue having two interactions with Salesforce in the same route like this? Does the AggregationStrategy that I use for enrich() need to do anything to the resource exchange to make it release the connection to Salesforce or anything else? Are there any significant bugs fixed in more recent versions (or unreleased versions) of the Salesforce code?