You need to sign in to do that
Don't have an account?
Itthiphum Lenavat
Connection Timeout: Custom .NET App
Hi All,
We’ve experience connection timeout starting about couple of weeks ago. We use custom .NET application using Salesforce SOAP Web Services. We get timeout error now in regular basis but note that “NOT” every time we make connection to Salesforce. We ran code review to point where it makes a call to Salesforce Web Services and error returned there. Here’s the query we use:
Select Id, IsDeleted, Name, CreatedDate, CreatedById, LastModifiedDate, LastModifiedById, SystemModstamp, Delivery__c, Delivery_Remain__c, Products__c, Delivery_Pcs__c, Product_Name__c, Order_Reference__c, Line_No__c, Part_No__c, Quantity__c, FOC_Quantity__c, Discount_Code__c, Discount_Percent_1__c, Discount_Percent_2__c, Discount_Percent_3__c, Unit_Price__c, List_Price__c, Discount_Item__c,Discount_Item_2__c, Discount_Order__c, Net_Amount_2__c, Vat_Amount_2__c, DO_Percent__c, Location__c, FOC_Act__c, Price_Level__c, Discount_Code_1__c, Discount_Code_2__c, Discount_Code_3__c, Discount_Code_4__c, FOC_Code_1__c, FOC_Code_2__c, FOC_Code_3__c, FOC_Code_4__c, FOC_Quantity_1__c, FOC_Quantity_2__c, FOC_Quantity_3__c, FOC_Quantity_4__c, Planner_Code__c,Price_3__c FROM Delivery_Line_Items__c WHERE Order_Reference__c in ('SW43-36383','SW43-36381','SW32-36370','SW32-36361','SW54-36345','SW31-36377','SW32-36371','SW31-36378','SW32-36367','SW32-36362','SW35-36376','SW33-36387','SW56-36359','SW41-36373','SW35-36375','SW33-36393','SW33-36388','SW32-36364','SW61-36355','SW46-36354','SW33-36391','SW32-36369','SW56-36360','SW43-36380','SW33-36385','SW61-36356','SW46-36353','SW32-36365','SW41-36374','SW33-36389','SW43-36384','SW33-36386','SW33-36392','SW43-36379','SW32-36372','SW56-36357','SW52-36368','SW56-36358','SW33-36390','SW43-36382','SW33-36395','SW55-36396','SW24-36363','SW42-36366','SW33-36394')
Please do “not” get overwhelm on the query, it’s a simple select using “in” in the WHERE clause. The target table is “Delivery_Line_Items__c”. Note that, using this same query in “Force.com Explorer”, we now sometimes get error also.
We’ve experience connection timeout starting about couple of weeks ago. We use custom .NET application using Salesforce SOAP Web Services. We get timeout error now in regular basis but note that “NOT” every time we make connection to Salesforce. We ran code review to point where it makes a call to Salesforce Web Services and error returned there. Here’s the query we use:
Select Id, IsDeleted, Name, CreatedDate, CreatedById, LastModifiedDate, LastModifiedById, SystemModstamp, Delivery__c, Delivery_Remain__c, Products__c, Delivery_Pcs__c, Product_Name__c, Order_Reference__c, Line_No__c, Part_No__c, Quantity__c, FOC_Quantity__c, Discount_Code__c, Discount_Percent_1__c, Discount_Percent_2__c, Discount_Percent_3__c, Unit_Price__c, List_Price__c, Discount_Item__c,Discount_Item_2__c, Discount_Order__c, Net_Amount_2__c, Vat_Amount_2__c, DO_Percent__c, Location__c, FOC_Act__c, Price_Level__c, Discount_Code_1__c, Discount_Code_2__c, Discount_Code_3__c, Discount_Code_4__c, FOC_Code_1__c, FOC_Code_2__c, FOC_Code_3__c, FOC_Code_4__c, FOC_Quantity_1__c, FOC_Quantity_2__c, FOC_Quantity_3__c, FOC_Quantity_4__c, Planner_Code__c,Price_3__c FROM Delivery_Line_Items__c WHERE Order_Reference__c in ('SW43-36383','SW43-36381','SW32-36370','SW32-36361','SW54-36345','SW31-36377','SW32-36371','SW31-36378','SW32-36367','SW32-36362','SW35-36376','SW33-36387','SW56-36359','SW41-36373','SW35-36375','SW33-36393','SW33-36388','SW32-36364','SW61-36355','SW46-36354','SW33-36391','SW32-36369','SW56-36360','SW43-36380','SW33-36385','SW61-36356','SW46-36353','SW32-36365','SW41-36374','SW33-36389','SW43-36384','SW33-36386','SW33-36392','SW43-36379','SW32-36372','SW56-36357','SW52-36368','SW56-36358','SW33-36390','SW43-36382','SW33-36395','SW55-36396','SW24-36363','SW42-36366','SW33-36394')
Please do “not” get overwhelm on the query, it’s a simple select using “in” in the WHERE clause. The target table is “Delivery_Line_Items__c”. Note that, using this same query in “Force.com Explorer”, we now sometimes get error also.
Amine H
i resolved this by doing a retry logic in my ETL job, here is how to http://talendexpert.com/tjavaflex-to-retry-salesforce-connection/