Salesforce.com API timeouts

Last Updated on Thursday, 31 May 2007 01:20 Written by Steve Thursday, 31 May 2007 01:20

About a month ago I started to get time out errors when I was using Eclipse to sync my S-Controls and when logging in to the Data Loader.

timeout.png

Increasing the timeout period does the trick, but I wonder why the timeouts have started happening more. I can’t help but think it’s tied to Apex going pre-release. Could be they’re being more sophisticated in how they’re prioritizing API traffic, favoring existing sessions over new ones.

Whatever the case may be, I recommend increasing your timeouts in Eclipse so you don’t get these annoying messages.

This entry was posted on Thursday, May 31st, 2007 at 1:20 pm and is filed under CRM, Technology. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

3 Comments

  1. Chris   |  Thursday, 31 May 2007 at 8:24 pm

    Hey Steve. Which version of the plugin are you using? What timeout setting is working best for you? Thanks.

    -Chris

  2. Dave   |  Friday, 01 June 2007 at 9:10 am

    Steve,

    If your timeout is low (as it is by default) in the Eclipse Toolkit and you have an ever increasing number of scontrols or other assets to sync, you will eventually hit the timeout. On the properties for your project there is a place where you can specify the timeout for the toolkit and that can be set to 600 seconds maximum.

  3. Steve   |  Friday, 01 June 2007 at 3:16 pm

    Thanks Dave. When I first ran into this, you helped me find that timeout setting and that did the trick. I did have the most timeouts in my instance with tons of S-Controls–nice to better understand that connection.

Leave a Reply