Alain, my problem was not to send an email, but was my server hanging up. I
thought Mandrill was blocking your server to process new requests.
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
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
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 tje message
Enviado através do AquaMail para Android
Sorry, truncated...
So... To make sure that the message doesn't get lost, I implemented a retry.
My diagnose is that the problem was with the connection and not properly
with Mandrill
Enviado através do AquaMail para Android
http://www.aqua-mail.com
A 12 de agosto de 2015 18:11:00 Moacir
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
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
Well, in that case, I would say it looks like a memory leak or something.
You say the socket should close in two minutes - are you leaving some
closures there too? Maybe those get piled up and then afterwards they only
accept new requests when old ones expire.
Did you count how many requests
Hi moacir, is there any socket process not completed to execute? Maybe it
can make your server not responding because main program wait the response
from socket.
On Aug 9, 2015 10:55 PM, zladuric zladu...@gmail.com wrote:
Well, in that case, I would say it looks like a memory leak or something.
A simple idea, but it might help:
Try to add logging middleware to your requests, which would also append
something you can recognize. Something
like https://github.com/villadora/express-bunyan-logger.
Then you might be able to compare which requests came in but are not
finishing, and so
Are you using webpack and sass-loader? On the request that hangs, are there
two or more places that import SCSS files? There are several issues posted
like this (server hangs, no error/warning):
https://github.com/jtangelder/sass-loader/issues/99
--
Job board: http://jobs.nodejs.org/
New
Hello Rob. I'm not using webpack nor sass.
Zladuric, I'm logging the connections and I found one service that usually
is involved with the problem, however when I restart the application, I
create a request with the same logged data, but the problem does not
reproduce. Strange, right? Not be
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
12 matches
Mail list logo
