You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Dalli Kranthi Kumar <da...@gmail.com> on 2018/01/31 12:52:39 UTC

Camel-salesforce Intermittent time outs

Hi,
  We are using the sales force component and trying to write to external salesforce health cloud using the camel salesforce component. Most of the times, the data seem to flow. However abruptly I see the below errors. If I reprocess the failed one again, it would work. But looks like this keeps happening a few times. Your suggestions, thoughts would be helpful.
 
 
2018-01-30 21:06:29.399 INFO 31221 — [[JPASalesForce]] c.f.s.s.processors.PatientProcessor : In PersonProcessor, Message received for patient MRN :: 5000307798
2018-01-30 21:06:29.401 INFO 31221 — [[JPASalesForce]] salesforce-route : Message Processed in AccountProcessor! Posting RequestBody to Salesforce :: {"HealthCloudGA_MedicalRecordNumberc":"5000307798","HealthCloudGASourceSystemId_c":"5000307798","BillingStreet":"2 SAPLING CIRCLES","BillingCity":"NASHUA","BillingState":"NH","BillingPostalCode":"03062","BillingCountry":"USA","ShippingStreet":"2 SAPLING CIRCLES","ShippingCity":"NASHUA","ShippingState":"NH","ShippingPostalCode":"03062","ShippingCountry":"USA","Phone":"605-101-0088","RecordTypeId":"012f40000009FE9AAM","Name":"Test, Zombie"}
2018-01-30 21:07:29.410 ERROR 31221 — [92963-scheduler] o.a.camel.processor.DefaultErrorHandler : Failed delivery for (MessageId: ID-hal-duffa-q03-dc-com-1517353893522-0-34236 on ExchangeId: ID-hal-duffy-q03-dc-com-1517353893522-0-34235). Exhausted after delivery attempt: 1 caught: org.apache.camel.component.salesforce.api.SalesforceException: Unexpected error {0:null} executing {PATCH:https://my.salesforce.com/services/data/v41.0/sobjects/Account/HealthCloudGA__SourceSystemId__c/5000307798 <https://my.salesforce.com/services/data/v41.0/sobjects/Account/HealthCloudGA__SourceSystemId__c/5000307798>}
Message History
---------------------------------------------------------------------------------------------------------------------------------------
RouteId ProcessorId Processor Elapsed (ms)
[salesforce-route ] [salesforce-route ] [activemq://queue:JPASalesForce ] [ 60064]
[salesforce-route ] [doTry6 ] [doTry ] [ 60010]
[salesforce-route ] [convertBodyTo1 ] [convertBodyTo[org.hl7.fhir.dstu3.model.Patient] ] [ 0]
[salesforce-route ] [process21 ] [ref:patientProcessor ] [ 2]
[salesforce-route ] [process22 ] [ref:accountProcessor ] [ 1]
[salesforce-route ] [log35 ] [log ] [ 0]
[salesforce-route ] [to8 ] [salesforce:upsertSObject?sObjectIdName=HealthCloudGA__SourceSystemId__c&sObjec] [ 60007]
Stacktrace
---------------------------------------------------------------------------------------------------------------------------------------
org.apache.camel.component.salesforce.api.SalesforceException: Unexpected error {0:null} executing {PATCH:https://my.salesforce.com/services/data/v41.0/sobjects/Account/HealthCloudGA__SourceSystemId__c/5000307798 <https://my.salesforce.com/services/data/v41.0/sobjects/Account/HealthCloudGA__SourceSystemId__c/5000307798>}
at org.apache.camel.component.salesforce.internal.client.AbstractClientBase$1.onComplete(AbstractClientBase.java:182) [camel-salesforce-2.20.1.jar:2.20.1]
at org.eclipse.jetty.client.ResponseNotifier.notifyComplete(ResponseNotifier.java:193) [jetty-client-9.4.7.v20170914.jar:9.4.7.v20170914]
at org.eclipse.jetty.client.ResponseNotifier.notifyComplete(ResponseNotifier.java:185) [jetty-client-9.4.7.v20170914.jar:9.4.7.v20170914]
at org.eclipse.jetty.client.HttpReceiver.terminateResponse(HttpReceiver.java:459) [jetty-client-9.4.7.v20170914.jar:9.4.7.v20170914]
at org.eclipse.jetty.client.HttpReceiver.abort(HttpReceiver.java:540) [jetty-client-9.4.7.v20170914.jar:9.4.7.v20170914]
at org.eclipse.jetty.client.HttpChannel.abortResponse(HttpChannel.java:129) [jetty-client-9.4.7.v20170914.jar:9.4.7.v20170914]
at org.eclipse.jetty.client.HttpChannel.abort(HttpChannel.java:122) [jetty-client-9.4.7.v20170914.jar:9.4.7.v20170914]
at org.eclipse.jetty.client.HttpExchange.abort(HttpExchange.java:257) [jetty-client-9.4.7.v20170914.jar:9.4.7.v20170914]
at org.eclipse.jetty.client.HttpConversation.abort(HttpConversation.java:141) [jetty-client-9.4.7.v20170914.jar:9.4.7.v20170914]
at org.eclipse.jetty.client.HttpRequest.abort(HttpRequest.java:748) [jetty-client-9.4.7.v20170914.jar:9.4.7.v20170914]
at org.eclipse.jetty.client.TimeoutCompleteListener.run(TimeoutCompleteListener.java:71) [jetty-client-9.4.7.v20170914.jar:9.4.7.v20170914]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_66]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_66]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_66]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [na:1.8.0_66]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_66]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_66]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_66]
Caused by: java.util.concurrent.TimeoutException: Total timeout 60000 ms elapsed
... 8 common frames omitted
2018-01-30 21:07:29.411 WARN 31221 — [[JPASalesForce]] o.a.c.c.jms.EndpointMessageListener : Execution of JMS message listener failed. Caused by: [org.apache.camel.RuntimeCamelException - org.apache.camel.component.salesforce.api.SalesforceException: Unexpected error \{0:null} executing \{PATCH:https://my.salesforce.com/services/data/v41.0/sobjects/Account/HealthCloudGA__SourceSystemId__c/5000307798}]
org.apache.camel.RuntimeCamelException: org.apache.camel.component.salesforce.api.SalesforceException: Unexpected error {0:null} executing {PATCH:https://my.salesforce.com/services/data/v41.0/sobjects/Account/HealthCloudGA__SourceSystemId__c/5000307798 <https://my.salesforce.com/services/data/v41.0/sobjects/Account/HealthCloudGA__SourceSystemId__c/5000307798>}
at org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(ObjectHelper.java:1831) ~[camel-core-2.20.1.jar:2.20.1]
at org.apache.camel.component.jms.EndpointMessageListener$EndpointMessageListenerAsyncCallback.done(EndpointMessageListener.java:195) ~[camel-jms-2.20.1.jar:2.20.1]
at org.apache.camel.component.jms.EndpointMessageListener.onMessage(EndpointMessageListener.java:116) ~[camel-jms-2.20.1.jar:2.20.1]
at org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:719) ~[spring-jms-4.3.12.RELEASE.jar:4.3.12.RELEASE]
at org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:679) ~[spring-jms-4.3.12.RELEASE.jar:4.3.12.RELEASE]
at org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:649) ~[spring-jms-4.3.12.RELEASE.jar:4.3.12.RELEASE]
at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:317) [spring-jms-4.3.12.RELEASE.jar:4.3.12.RELEASE]
at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:255) [spring-jms-4.3.12.RELEASE.jar:4.3.12.RELEASE]
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1166) [spring-jms-4.3.12.RELEASE.jar:4.3.12.RELEASE]
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1158) [spring-jms-4.3.12.RELEASE.jar:4.3.12.RELEASE]
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:1055) [spring-jms-4.3.12.RELEASE.jar:4.3.12.RELEASE]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_66]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_66]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_66]
Caused by: org.apache.camel.component.salesforce.api.SalesforceException: Unexpected error {0:null} executing {PATCH:https://my.salesforce.com/services/data/v41.0/sobjects/Account/HealthCloudGA__SourceSystemId__c/5000307798 <https://my.salesforce.com/services/data/v41.0/sobjects/Account/HealthCloudGA__SourceSystemId__c/5000307798>}
at org.apache.camel.component.salesforce.internal.client.AbstractClientBase$1.onComplete(AbstractClientBase.java:182) ~[camel-salesforce-2.20.1.jar:2.20.1]
at org.eclipse.jetty.client.ResponseNotifier.notifyComplete(ResponseNotifier.java:193) ~[jetty-client-9.4.7.v20170914.jar:9.4.7.v20170914]
at org.eclipse.jetty.client.ResponseNotifier.notifyComplete(ResponseNotifier.java:185) ~[jetty-client-9.4.7.v20170914.jar:9.4.7.v20170914]
at org.eclipse.jetty.client.HttpReceiver.terminateResponse(HttpReceiver.java:459) ~[jetty-client-9.4.7.v20170914.jar:9.4.7.v20170914]
at org.eclipse.jetty.client.HttpReceiver.abort(HttpReceiver.java:540) ~[jetty-client-9.4.7.v20170914.jar:9.4.7.v20170914]
at org.eclipse.jetty.client.HttpChannel.abortResponse(HttpChannel.java:129) ~[jetty-client-9.4.7.v20170914.jar:9.4.7.v20170914]
at org.eclipse.jetty.client.HttpChannel.abort(HttpChannel.java:122) ~[jetty-client-9.4.7.v20170914.jar:9.4.7.v20170914]
at org.eclipse.jetty.client.HttpExchange.abort(HttpExchange.java:257) ~[jetty-client-9.4.7.v20170914.jar:9.4.7.v20170914]
at org.eclipse.jetty.client.HttpConversation.abort(HttpConversation.java:141) ~[jetty-client-9.4.7.v20170914.jar:9.4.7.v20170914]
at org.eclipse.jetty.client.HttpRequest.abort(HttpRequest.java:748) ~[jetty-client-9.4.7.v20170914.jar:9.4.7.v20170914]
at org.eclipse.jetty.client.TimeoutCompleteListener.run(TimeoutCompleteListener.java:71) ~[jetty-client-9.4.7.v20170914.jar:9.4.7.v20170914]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[na:1.8.0_66]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:1.8.0_66]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) ~[na:1.8.0_66]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) ~[na:1.8.0_66]
... 3 common frames omitted
Caused by: java.util.concurrent.TimeoutException: Total timeout 60000 ms elapsed
... 8 common frames omitted

Re: Camel-salesforce Intermittent time outs

Posted by Zoran Regvart <zo...@regvart.com>.
Hi Dalli,
you can increase the timeout from the default 60000 milliseconds to
any greater value that would result in a successful invocation by
putting "timeout" and a numeric value in the `httpClientProperties`[1]
map in the component configuration.

This might not solve your issue entirely as the request the Camel
Salesforce component made against the Salesforce API took longer that
the default timeout and might take longer than any other timeout you
set.

This is entirely an issue of the server side processing done at
Salesforce or any other system Salesforce subsequently interacts with.

And please do not use JIRA to ask questions, we use JIRA to track
issues and it is difficult enough to use it for that without the added
noise of non-issue posts. There are plenty of ways to get prompt
response from Q&A sites like Stackoverflow[2] or by enlisting the
services of companies that offer commercial support[3]. We have a
helpful guide on how to get support as well[4] that you are encouraged
to read.

zoran

[1] https://github.com/apache/camel/blob/master/components/camel-salesforce/camel-salesforce-component/src/main/docs/salesforce-component.adoc#options
[2] https://stackoverflow.com/questions/tagged/apache-camel
[3] https://camel.apache.org/commercial-camel-offerings.html
[4] https://camel.apache.org/support.html
-- 
Zoran Regvart