How does one avoid ETIMEDOUT errors?

74 views
Skip to first unread message

Gregory Pierce

unread,
Aug 19, 2015, 7:19:15 PM8/19/15
to OrientDB
I've seen this being discussed in a number of places but I haven't seen a solution to it yet.

I'm having an issue where database connections are getting stale and after some time requests from Javascript's Oriento driver will generate the infamous:

read ETIMEDOUT


For example:


Error (E_UNKNOWN) :: Encountered an unexpected error\nOrientDB.ConnectionError [2]: read ETIMEDOUT\n    at Connection.handleSocketError (/opt/foobar/node_modules/sails-orientdb/node_modules/oriento/lib/transport/binary/connection.js:294:63)\n    at Socket.emit (events.js:95:17)\n    at net.js:441:14\n    at process._tickDomainCallback (node.js:492:13)\n\nDetails:  OrientDB.ConnectionError [2]: read ETIMEDOUT\n'


...


OrientDB.ConnectionError [2]: read ETIMEDOUT

    at Connection.handleSocketError (/opt/foobar/node_modules/sails-orientdb/node_modules/oriento/lib/transport/binary/connection.js:294:63)

    at Socket.emit (events.js:95:17)

    at net.js:441:14

    at process._tickDomainCallback (node.js:492:13)




What is going on with this? Its not clear what the issue is nor what should be done about it.

Reply all
Reply to author
Forward
0 new messages