ECONNRESET

I get these errors sometimes. Randomly.

    Error: read ECONNRESET 
        at exports._errnoException (util.js:742:11) 
        at TCP.onread (net.js:535:26)

and

    Error: write ECONNRESET 
        at exports._errnoException (util.js:742:11) 
        at Object.afterWrite (net.js:749:14) 

I read somewhere that this also happens on node-mysql, but that it could be fixed by using pool. I began using pool, but it still happens.

Suggestions?

[farzher]

for anyone getting this error randomly. i guess you’re supposed to write this wrapper around pool.query (or whatever call you’re using). stops the problem for me.

function query_with_retries(sql, params, retries_left=1) {
  try {
    return pool.query(sql, params)
  } catch(err) {
    if(retries_left >= 1 && err.code === 'ECONNRESET') {
      console.error({msg:'query_with_retries retrying!', retries_left, err})
      return query_with_retries(sql, params, retries_left-1)
    } else {
      throw err
    }
  }
}

[jsbinette]

For one I agree that this driver should have a ‘keep alive’ option.  It’s hard to debug and there are no ‘using’ keyword like c# that makes it easy o handle in JavaScript

Thursday, January 10, 2019, 6:42 PM -0500 from [e-mail] [e-mail]:

@farzher this is a low level driver and retries out of the scope. It’s not clear from your report if you can catch and process error in your code or it’s something that your code can’t handle ( if latter, it definitely need to be fixed ) The “best practise” usually is to never use individual connections directly and use connection pool ( even if one connection is enough from perf point of view ). But even with pool you absolutely must be able to handle errors from production code and make a decision what to do ( retry / log / report to user ) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub , or mute the thread .