Postgres adapter failng with read ETIMEDOUT error

Not applicable

I have a ruby script that makes repeated calls to a local postgres adapter with a node.js interface. I more or less used the sample provided and made small changes for my situation.

The script runs fine for the first ~200 requests, but now I seem to be getting an error every time I run it:

Error: read ETIMEDOUT

    at errnoException (net.js:904:11)

    at TCP.onread (net.js:558:19)

I can't find anything odd or different from the calls that fail. As far as I can tell, the request that failed the last time was:

select account_id, name_first, name_last from sfdc.contacts WHERE email_address = 'Epsteins_Mutha@yahoo.com' LIMIT 100

The query to rest map is as follows:

module.exports = {
  'orgs': {
    queryStringBasic: 'SELECT org_name FROM metrics.org_users',
    queryParameters: {
      email: 'email_address = \'{email}\''
    }
  },
  'org_accounts': {
    queryStringBasic: 'SELECT account_name FROM reference.v_org_account',
    queryParameters: {
      org_name: 'org_name = \'{org_name}\''
    }
  },
  'contacts': {
    queryStringBasic: 'select account_id, name_first, name_last from sfdc.contacts',
    queryParameters: {
      email: 'email_address = \'{email}\'' 
    },
  },
  'contacts_verbose': {
    queryStringBasic: 'select name_first, name_last from sfdc.contacts',
    queryParameters: {
      email: 'email_address = \'{email}\'' 
    },
  },
  'leads': {
    queryStringBasic: 'select email, fullname from sfdc.leads',
    queryParameters: {
      email: 'email = \'{email}\'' 
    },
  },
  'leads_verbose': {
    queryStringBasic: 'select email, fullname from sfdc.leads',
    queryParameters: {
      email: 'email = \'{email}\'' 
    },
  },
  'accounts': {
    queryStringBasic: 'select id, account_name, sales_stage from sfdc.accounts',
    queryParameters: {
      account_id: 'id = \'{account_id}\''
    }
  }
}

Any help or advice would be appreciated. This has been working without any problems for months. I did see the problem once in July but when I ran the script it went through cleanly. Now it seems to be failing every time. There doesn't seem to be any particular record that it is failing on.

0 0 557
0 REPLIES 0