Jérémy, I have Tcpview, a GUI tool to monitor it, but I restarted the server today... so, I need to wait to see this problem again to confirm your question. Probably, it will happen again in the next two or three days, I hope...
My server doesn't have many connections, but I have tried to reproduce this error using some attack tools, however always unsuccessful. Christian, I'm using a pre-compiled version of node.js for Windows. In my code, I do not use the vm module. The problem is that I can't see where the code is hanging, the debug just doesn't work, it's terrible. Do you have any ideia how to debug in this cases? On Friday, August 7, 2015 at 12:51:17 PM UTC-3, Moacir Braga wrote: > > It’s been a few weeks since I started trying to solve this problem, but I > still haven’t figured out a possible solution. The issue is that my server > accepts requests and responds to them normally in the beginning. However, > after an unknown event happens (I’m still trying to discover which event it > is), the server continues accepting requests, but it stops responding to > them. > > > > I’ve already checked the Process Monitor (the server is running on Windows > Server 2012 R2) and I could notice that when this problem happens, new > requests generate a TCP Accept, a TCP Receive, but not a TCP Send nor a > Disconnect. > > > > I tried to execute the server in debug mode, but then again, when this > problem happens the debugger does not work and it hangs up as well. > > > > The server doesn’t explode and no errors occur. Thus, domains won’t help > me in this case. I’ve tried to handle uncaughtException, but it also didn’t > work. > > > > The server keeps running without using excessive processor or memory > resources. Its behavior is still similar to the one during the first > execution, except for the fact that it’s not responding as it was before. > > > > When I sent a SIGNAL via console, the server simply started working > normally again without restarting or anything. It just got back to normal. > > > > I tried to execute a lot of requests using ApacheBench and NeoLoad, but I > just can’t reproduce this problem. It simply happens randomly. > > > > The socket has a timeout of two minutes. However, the server keeps hanging > up the requests for hours. > > > > When I sent the SIGNAL mentioned before, all requests that were hanging > were executed, as if they were in a queue waiting for the last request to > be finished. > > > > I don’t know what else could I do to find out what is causing this problem. > > > I'm using Node.js + Express + body-parser + cookie-parser + Windows > Server 2012 R2 x64 with GUI + Amazon EC2 micro instance. > > > *If somebody has any idea of what is causing the server to hang up > forever, please tell me.* > > > Best Regards, > > *Moacir Braga* > -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: 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 unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. To post to this group, send email to nodejs@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/8b12f826-379b-4eb5-9cb0-0533857fdd46%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
