On Mon, Feb 6, 2012 at 16:25, NodeJazz <infinic...@gmail.com> wrote: > Hi, > > I am running node 0.6.8 on Windows Server 2008 R2. I have a basic 6 > worker clustered http server script serving a static file using > stream.pipe. I have 13000 http connections attempting to retrieve the > static file 60 times over a period of 2 minutes. As the number of > connections increase some of the workers die due to an unknown error. > The messages from node as follows: > > > C:\files>"C:\Program Files (x86)\nodejs\node.exe" "C:\Program Files > (x86)\nodejs\hs.js" > > stream.js:105 > throw er; // Unhandled stream error in pipe. > ^ > Error: OK, success 'C:\files\test.dat' > worker 17104 died > > stream.js:105 > throw er; // Unhandled stream error in pipe. > ^ > Error: OK, success 'C:\files\test.dat' > worker 18884 died > > stream.js:105 > throw er; // Unhandled stream error in pipe. > ^ > Error: OK, success 'C:\files\test.dat' > worker 14100 died > > Would you have any hints or advice concerning the problem?
You need to attach an error event listener to the stream. Connections may terminate unexpectedly for a number of reasons. If you don't handle the error, you'll get the behaviour you're seeing now. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
