Hi,
Can you please confirm that:
- it is node.js giving the error and not the database server?
If this is right, I fear this has nothing to do with ArangoDB or arangojs, see
This seems to be an unresolved issue of node.js on Windows. This links to
and
which suggest the same. There seems to be a workaround for OSX, but none for Windows.
What happens, if you delay the calls to arangojs a bit?
Best regards,
Max.