Question

I am working on Opa app using CouchDB as a database backend. When fetching a document with API function CouchDd.Document.get (API doc) and the DB server is down, my app crashed:

/opt/mlstate/lib/opa/stdlib/server.opp/serverNodeJsPackage.js:169
,(global.hasOwnProperty("toString") && global.toString || undefined)(e));}req.
                                                                    ^
TypeError: undefined is not a function
    at ClientRequest.on_error (/opt/mlstate/lib/opa/stdlib/server.opp/serverNodeJsPackage.js:169:489)
    at ClientRequest.EventEmitter.emit (events.js:88:17)
    at Socket.socketErrorListener (http.js:1320:9)
    at Socket.EventEmitter.emit (events.js:88:17)
    at Socket._destroy.self.errorEmitted (net.js:329:14)
    at process.startup.processNextTick.process._tickCallback (node.js:244:9)

and returns to shell prompt. I am running the app with ./myapp --nodb, because I do not use the build-in support for the MongoDB.

The CouchDb.Document.get function returns either {success: {FormatedJson: ...}} or {failure}. I expected that parsing the result for the {failure} is enough to catch all the network connection problems. What else should I do?

I am using Opa framework version 1.0.5 on OSX (11.4.0 Darwin) from the standard package on the Opa website, Node.js v0.8.3 and CouchDB 1.2.0.

Answer 1

This was a bug in 1.0.5, but it’s been fixed already. You can get the sources for the fixed version here, but an official package hasn’t been released yet.