That application is very old, in asp classic and badly written. The page
was aborting because of an error sending the email. Implementing a
try-catch (it's equivalent in asp) solved the problem.
But to make sure that the message doesn't get lost, I implemented a
retry, it waits 3s each time and repeats 10 times for a total os 30 seconds.
My diagnose is that the problem was with the connection and not properly
with Mandrill.
(may previous email gos truncated and uplicated and never got to the
list, so this is a consolidated version)
Alain Mouette
=== Projetos especiais: <http://lnkd.in/dEu8cNq> ===
Em 12-08-2015 18:04, Moacir Braga escreveu:
Hi Alain, your answer makes me happy because if Mandrill is the
problem, many things will make sense to me, but I need to ask you
something.
The problem you mentioned before was a completely hanging up server?
I didn't understand very well your comment "10 retries as 30s
interval". Why did you decided to implement this solution? Analyzing
your comment I understood that Mandrill is entering in a infinite loop
and blocking the main process.
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
<mailto:nodejs+unsubscr...@googlegroups.com>.
To post to this group, send email to nodejs@googlegroups.com
<mailto:nodejs@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/nodejs/afac9a62-d246-4a27-b2fc-bd800165d986%40googlegroups.com
<https://groups.google.com/d/msgid/nodejs/afac9a62-d246-4a27-b2fc-bd800165d986%40googlegroups.com?utm_medium=email&utm_source=footer>.
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/55CBED66.8080808%40bonseletrons.com.br.
For more options, visit https://groups.google.com/d/optout.
