if your running on joyent just open cloud analytics and tada! If your running on solaris just use dtrace hooks and tada!
If your on smartos / joyent you can just gcore the process and open it in mdb to get the stacktrace and the heap state For the "why has my event loop not shut down case in my unit tests" you probably need a clever trick or a C++ addon that hooks into libuv +1 for the "tell me what is spinning on the event loop not closing this test" module. Someone should write that. On Tue, Jan 15, 2013 at 9:55 AM, Mooky <[email protected]> wrote: > > On occasion we have our node app become unresponsive - and I'm > struggling to find information how we can go about monitoring what's > happening in the internals of node (e.g. its event queue depth, IO > state, what the event loop is currently doing, etc) so we can get a > clue on what is wrong. > > We also have occasion when our nodeunit tests fail to stop - and we > cant work out what is still "running" within node (e.g. some > connection we have failed to close or some scheduled loop we have > failed to stop) - and again we are looking for some visibility on > whats happening in node. > > Any pointers? > > -- > 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 > -- 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
