My code creates a mail message and adds it to a collection.
Then in a forked process I read the collection of messages one by one and
attempt to send them.
It uses a timer to wait and try again, stopping only when the message
collection is empty.
I can share my code (it's far from enterprise stre
Since JRMPC opens for registration in three days, I can't afford to screw
around with the web server at this late date. Had I known about this issue
earlier in the year (say, May or June), I could've dealt with it then.
All I'm looking for is a workaround, a duct tape solution.
Sven Van Caekenb
> On 1 Sep 2019, at 23:06, horrido wrote:
>
> This didn't fix the issue. It's not a matter of adjusting timeout values.
>
> However, I believe I've resolved the matter, more or less. You see, I think
> the problem is with Gmail...
>
> My Teapot application is using
> ZdcSecureSMTPClient>>sen
> On 3 Sep 2019, at 00:54, Jeff Gray wrote:
>
> Have you tried manually opening up the gmail account you are sending from in
> the browser and looking for anything funny? I have had similar issues where
> the gmail was needing a security prompt/response.
> I wrote a service to send mails async
Have you tried manually opening up the gmail account you are sending from in
the browser and looking for anything funny? I have had similar issues where
the gmail was needing a security prompt/response.
I wrote a service to send mails asynchronously (in case the gmail connection
was down and genera
This didn't fix the issue. It's not a matter of adjusting timeout values.
However, I believe I've resolved the matter, more or less. You see, I think
the problem is with Gmail...
My Teapot application is using
ZdcSecureSMTPClient>>sendUsingGmailAccount:password:to:message:. For
whatever reason, G
I did a bit of research on the web and I discovered that nginx can be
unreliable due to default or inappropriate settings for certain timeout
values. Currently, I'm testing a possible fix: set /keepalive_timeout/ to
90, rather than the default 65. So far, it seems to work, but I need further
testin
On Wed, 28 Aug 2019 at 03:12, Richard Kenneth Eng
wrote:
> I have a Teapot application running under Linux and nginx. From time to
> time, I get the following error: *ConnectionTimedOut: Data receive timed
> out.*
>
> Otherwise, the Teapot application works fine, even with this error message.
>
>
I have a Teapot application running under Linux and nginx. From time to
time, I get the following error: *ConnectionTimedOut: Data receive timed
out.*
Otherwise, the Teapot application works fine, even with this error message.
Can anyone tell me what or where it's timing out, and how can I change
