Hi,
It's the client that closes the connection, you can see some
disconnectExceptions in the client log, however it would be nice if there was a
log: "Closing connection due to request timeout" somwhere. This would save me
some time parsing wireshark logs, though when you look at that carefully you
see it's the client closing. But when you diagnose something that happens in
the production it's always a bit more stressfull, so you can miss such things
(wireshark captures are not known for bravity).
Regards,Goran
On Saturday, May 2, 2020, 03:33:24 PM GMT+2, Liam Clarke-Hutchinson
<liam.cla...@adscale.co.nz> wrote:
Hi Goran,
Glad you figured it out :) And interesting that there was nothing in the
server logs (as far as I can tell, it's a bit hard to read) which showed
why the server was terminating the connection. Just wanted to provide
feedback that your second attempt at sending the logs was really hard to
read also. Could I suggest something like pastebin.com or gist.github.com
for future issues? They keep the formatting intact and make it easier to
delve into your logs.
Cheers,
Liam Clarke-Hutchinson
..
