Ever since we were upgraded to Winter '16, our Accounts integration has been experiencing this issue :

Unable to connect to Salesforce.com after 5 attempts.
Error is: java.net.SocketTimeoutException: Read timed out.

Are there any known performance issues with integration processing on Winter '16? This integration has been working fine for 5 years, and now all of a sudden we are experiencing this issue frequently. Sometimes only 1 batch of 200 upserts will process OK, and then with the next execution 2-3 batches will process successfully before failing on the issue above.

We have the integration connecting to :

https://login.salesforce.com/services/Soap/u/29.0

Is there a newer API level we should be logging in to?
Thanks for any ideas or thoughts concerning this recent problem.

Miki Tosic
Life Fitness

We use IBM WebSphere Cast Iron to integrate to SFDC. Our Accounts integration executes once per hour, 24x7, and in general processes all data with few issues other than the expected various data issues. However, once per month we run a larger than normal 'upsert' process (i.e. 1000-3000 upserts), and invariably a significant portion of these experience :

UNABLE_TO_LOCK_ROW
unable to obtain exclusive access to this record

Can anyone offer any ideas on what to look for here? We never experience this error with the regular hourly executions (i.e. 50-300 upserts). What could possibly cause the lock issue in this situation? What should be looked for? Is there any way to resolve this issue?

Thanks a lot for any assistance.

Miki Tosic
Life Fitness

We use IBM WebSphere Cast Iron to integrate to SFDC. Our Accounts integration executes once per hour, 24x7, and in general processes all data with few issues other than the expected various data issues. However, once per month we run a larger than normal 'upsert' process (i.e. 1000-3000 upserts), and invariably a significant portion of these experience :

UNABLE_TO_LOCK_ROW
unable to obtain exclusive access to this record

Can anyone offer any ideas on what to look for here? We never experience this error with the regular hourly executions (i.e. 50-300 upserts). What could possibly cause the lock issue in this situation? What should be looked for? Is there any way to resolve this issue?

Thanks a lot for any assistance.

Miki Tosic
Life Fitness

Are the IP address ranges listed here :

https://help.salesforce.com/HTViewSolution?id=000003652&language=en_US (https://help.salesforce.com/HTViewSolution?id=000003652&language=en_US)

for end user connectivity via web browser, or integration applications, or both? I'm interested in the discrete list of IP addresses available for integrations connectivity/processing (not end user use). Thanks, Miki.

We use IBM WebSphere Cast Iron to integrate between our internal databases and Salesforce.com. Where can I obtain the Salesforce.com IP addresses that should be whitelisted by our company for integrations connectivity and processing? This would include processing regarding Accounts, Assets, Contacts, Opportunities, and Quotes. Thanks, Miki.

For Accounts, Assets, Contacts, and Quotes SFDC API logins we currently use :

 

https://login.salesforce.com/services/Soap/u/29.0

 

1) Is this current?

 

2) Where can I read more about this topic?

 

3) What is the best way to make sure we stay current in the future?

 

Thanks, Miki.

 

 

1) For Assets we currently access : https://salesforce.com/services/Soap/c/20.0/0DF80000000H0Xd

Is this current for Assets?
If not, what is the current URL for Assets processing?
If not, where can I read further about current Salesforce.com Assets API processing?

2) For Quotes we currently access : https://salesforce.com/services/Soap/c/18.0/0DFQ00000008PE9

Is this current for Quotes?
If not, what is the current URL for Quotes processing?
If not, where can I read further about current Salesforce.com Quotes API processing?

Thank you.

Only very recently our Cast Iron integrations report the following failure message at random times, usually when attempting to login to SFDC :

 

Error message: Unrecognized SSL message, plaintext connection?.  Caused by: Unrecognized SSL message, plaintext connection?

 

We have been live with these integrations in production since 2010, and have never seen these messages until Nov. 2013.

Can anyone shed any light on what this failure actually means, and what corrective action we may need to take in order to prevent this from happening in the future?

 

Thanks very much for your time, Miki.

We use IBM WebSphere Cast Iron to integrate to SFDC. Our Accounts integration executes once per hour, 24x7, and in general processes all data with few issues other than the expected various data issues. However, once per month we run a larger than normal 'upsert' process (i.e. 1000-3000 upserts), and invariably a significant portion of these experience :

UNABLE_TO_LOCK_ROW
unable to obtain exclusive access to this record

Can anyone offer any ideas on what to look for here? We never experience this error with the regular hourly executions (i.e. 50-300 upserts). What could possibly cause the lock issue in this situation? What should be looked for? Is there any way to resolve this issue?

Thanks a lot for any assistance.

Miki Tosic
Life Fitness

We use IBM WebSphere Cast Iron to integrate between our internal databases and Salesforce.com. Where can I obtain the Salesforce.com IP addresses that should be whitelisted by our company for integrations connectivity and processing? This would include processing regarding Accounts, Assets, Contacts, Opportunities, and Quotes. Thanks, Miki.

For Accounts, Assets, Contacts, and Quotes SFDC API logins we currently use :

 

https://login.salesforce.com/services/Soap/u/29.0

 

1) Is this current?

 

2) Where can I read more about this topic?

 

3) What is the best way to make sure we stay current in the future?

 

Thanks, Miki.

 

 

Only very recently our Cast Iron integrations report the following failure message at random times, usually when attempting to login to SFDC :

 

Error message: Unrecognized SSL message, plaintext connection?.  Caused by: Unrecognized SSL message, plaintext connection?

 

We have been live with these integrations in production since 2010, and have never seen these messages until Nov. 2013.

Can anyone shed any light on what this failure actually means, and what corrective action we may need to take in order to prevent this from happening in the future?

 

Thanks very much for your time, Miki.