substack/bouncy — Issue #16: Bouncy in CLI mode breaks when the destination port is broken
Author: aldeluis
Created: 2011-12-09 17:49:42+00:00
State: open

Maybe in CLI mode boucy could emit a 502 or 503 error without exiting in order to keep the other routes functional for a production environment. Thank you for your work, bouncy is great!

node.js:183
throw e; // process.nextTick error, or 'error' event on first tick
^
Error: EPIPE, Broken pipe
at Socket._writeImpl (net.js:159:14)
at Socket._writeOut (net.js:451:25)
at Socket.flush (net.js:530:24)
at Socket._onWritable (net.js:610:12)
at Socket._onConnect (net.js:598:12)
at IOWatcher.onWritable [as callback] (net.js:186:12)