Isaac, That is interesting information. It is not in the docs afaict: http://nodejs.org/api/stdio.html. A note in the docs about what happens to in-flight messages to stdio when node crashes would help. If it's there already and I missed it please accept my headsmack.
Thanks, -g On Thursday, March 21, 2013 5:19:08 PM UTC-7, Isaac Schlueter wrote: > > > and "console.error" is more of a friend than console.log in locking > cases. It is output immediately (so it will slow your server down a tad > since it is sync rather than async) but you don't loose any messages > > console.log is synchronous as well, has been since 0.6, iirc. > > > > On Thu, Mar 21, 2013 at 2:58 PM, Nathanael Anderson > <[email protected] <javascript:>> wrote: > > > > > > On Thursday, March 21, 2013 4:26:59 PM UTC-5, Lars Jacob wrote: > >> > >> We recently encountered an issue with our node.js application (based in > >> express.js and socket.io). After a while the application won't respond > to > >> any I/O or if only erratically. It still accepts tcp connections (or > http > >> connections) but doesn't respond at all. Furthermore it can't establish > >> network connections to the outside world. For example we see "failed to > >> connect to mongodb" which is triggered by a database query which is > called > >> within a setInterval callback. And we are seeing this logs only because > >> after a while the server stops to be "locked" and continues to work > fine... > >> > >> Has anybody seen a similar behaviour? I know it's a pretty vague > >> description but until now we were unable to track this down further. > Any > >> Ideas? > >> > >> We could reproduce this with our application in node 0.8.17 and 0.8.22 > >> > >> Thanks for your help in advance! > >> Lars > > > > > > Adding lot of logging -- and "console.error" is more of a friend than > > console.log in locking cases. It is output immediately (so it will > slow > > your server down a tad since it is sync rather than async) but you don't > > loose any messages. One thing to track is how many connections you > have > > (both http & socket) that are currently active and how many connections > you > > have active to mongo (any any other things like memcache)... You might > be > > finding that one of your pools is not releasing resources. > > > > Nathanael A. > > > > -- > > -- > > 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 [email protected]<javascript:> > > To unsubscribe from this group, send email to > > [email protected] <javascript:> > > For more options, visit this group at > > http://groups.google.com/group/nodejs?hl=en?hl=en > > > > --- > > You received this message because you are subscribed to the Google > Groups > > "nodejs" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to [email protected] <javascript:>. > > For more options, visit https://groups.google.com/groups/opt_out. > > > > > -- -- 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
