Node stopping any sending after a while it runs

[Tony Mobily]

Hi,

An application I developed seems to stop sending pages out after a while (see; A few hours) of running. Debugging this is really hard, because it only happens after a few hours -- and I cannot really add any debug info. I haven't ben able to make this easier than reproduce, other than "run the application and wait a few hours". At ths rate, it will take me 1 month to debug.

Basically any URL returns no data.

The only clear symptom I have is that the logger also goes bananas, and starts returning

GET /stores/tabs/dispatcher/5502177028b15d7117b0c1ed - - ms - -

GET /stores/tabs/dispatcher/5502177028b15d7117b0c1ed - - ms - -

GET /stores/tabs/dispatcher/5502185828b15d7117b0c1f1 - - ms - -

GET /app/auth/welcome - - ms - -

The database server is still responsive.

I am not sure what to do... any ideas or hints would be most welcome!

Merc.

[Toby Corbin]

Hi,

The IBM SDK for Node.js http://www.ibm.com/developerwo... which is community node with support for IBM's free tooling, ships with the Health Center monitoring agent npm pre installed. This gives you live GC monitoring, CPU usage and method profiling via the Health Center client http://www.ibm.com/developerwo... and available from the eclipse marketplace http://marketplace.eclipse.org.... We are looking at making this available outside of the IBM SDK for Node.js as this is extremely useful for detecting memory leaks and performance problems.  The method profiling view could well help you as it will let you know which methods you are spending most of your time in and so it could shed light on where your program is hanging