Transport layer timeout on query after a period of inactivity

[phpnode]

From @osklyar on April 1, 2015 13:5

A query made with a once initialized and kept in that state DB object (var db = oriento({...}).use("somedb")) is running into a timeout at the transport socket level, [OrientDB.ConnectionError [2]: read ETIMEDOUT], first time I make a DB query after a longish period of inactivity between two DB access operations. A pause of 30min or so triggers the issue. Right after the timeout error the connection is somehow re-initialized and the next query runs fine. At the moment I solve the problem by scheduling a trivial select from ouser every minute, which is a fairly ugly workaround.

The expected behavior is for the driver to make sure the connection is alive and reestablish it when necessary without a long wait for the timeout and without timeout exceptions.

I might be missing some configuration option, and would be grateful for any hints what I should configure to reach the expected behavior.

See the original post at StackOverflow http://stackoverflow.com/questions/29257860/avoid-query-timeout-in-oriento-node-js-driver-for-orientdb

Copied from original issue: codemix/oriento#298

[TheAdamGalloway]

Does anybody have a solution for this issue? I've been encountering it in my app after periods of inactivity. It's annoying since it throws an Error.