Connection failure when trying to get multiple Leads

[Anonymous]

Hi all,

We recently have been noticing a connection failure when trying to extract LeadRecord by 'getMultipleLeads()'. Error message reads as: “The underlying connection was closed: An unexpected error occurred on a receive.”
On multiple attempts (5+), ultimately a connection can be made and data extraction process can begin.
Most of the time, error occurs prior to any records being extracted, but at times it also happens after a subset of records have been extracted.
Any suggestions?

Thanks,
Biao

[Kenny_Elkington]

Hey Biao,

Is this exclusive to get multiple leads, or is this occurring with other methods as well?

[Anonymous]

Hi Kenny,

We're just using the APIs  getMultipleLeads() a little frequently (and describeMObject() sometimes) in our integration, so I haven't met exception with other methods.

Thanks,
Biao

[Anonymous]

Biao - Can you share the request XML you are sending when you recieve this connection error?

[Anonymous]

Hi Travis,
 
In our Integration, I add the WSDL to Service References in a C# project in VS2010. We extract data by calling the function ‘getMultipleLeads’ with specified parameters. So there is no XML could be shown. (The request XML would be auto-created by Web Service of dotNET Framework)
 
In another hand, it’s hard to say which request would be failed. When I do the unit tests, it works well. When it is used for our user cases in Piyush’s part (large number of Leads cause multiple requests), it works well at the beginning. Some time, the connection failure occurs. But retrying the same request after a while (how long is not sure), would be succeeded.

Thanks,
Biao

[Anonymous]

Hi Biao - Connection issues may occur, so your best course of action is to make sure that you have reasonable retry logic in place.

[Anonymous]

Thank you very much, Travis.
Then, what's your suggestions about the time interval sleeping after one failure and the max count of retrying times?
And how could I know whether one failure could be resolved by retrying it or it is a real connection error that needs to stop it?

For an additional question, Are there any limitations of requests should be noticed? For example, min time interval between two requests, max requests count in 24 hours, and so on.

Thanks,
Biao