Hi, I am using Mandrill in one other application. I had some problems until
I started checking for errors and implemented 10 retries as 30s interval.
After that I never had problems again...
Enviado através do AquaMail para Android
http://www.aqua-mail.com
A 12 de agosto de 2015 16:39:30 Moacir Braga <cont...@moacirbrg.org> escreveu:
Sorry for my late, but I was monitoring the server after I restarted it
last friday, but so far no problem happened again.
Zlatko:
- I checked the http.globalAgent.maxSockets and it is setted to Infinity
(default in Node 0.12.7).
- I'm using a third-party service (Mandrill), by the way, maybe it is the
problem, I don't know, I'll remove it and put a simple SMTP library instead.
- No, I didn't count how many requests because it's really random,
sometimes hangs up after few hours, sometimes after few days, but your
suggestion is really good for many purposes and I'll implement it.
Boby:
- Really good question, I'm using Tcpview to figure out, but nothing is
open when the problem happens.
- The server has a timeout of two minutes, in other words, if some socket
still opened for a while, the main program will wait only for two minutes
and will terminate the hanged connection.
When I restarted the server last friday, this problem doesn't happen
anymore, maybe something in Windows was hanging node process, I don't know.
One change I made was remove setInterval from my code, this timer was used
to remove invalid sessions. After some tests I figured out that setInterval
hangs up the console, but I can't believe in a direct relation between
setInterval and a hanged response. I don't know if this change together a
server restart was what helped me...
So, I'll be monitoring the server and if the problem happens again, I'll
notify you to confirm that isn't the timer.
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/3a4ac85f-4ae6-46cb-8806-c5081fccc1df%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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/14f23721050.2782.962c06d43ba9274da034cf7d02472879%40bonseletrons.com.br.
For more options, visit https://groups.google.com/d/optout.
