Please reply to the list rather than to me directly.
> From: Kamala Ayyar
> Sent: Thursday, 26 August, 2021 08:57
> We call the WSAGetLastError immediately after SSL_ERROR_SYSCALL and we get
> the
> WSAETIMEDOUT
OK. This wasn't entirely clear to me from your previous message. So you are
> From: Kamala Ayyar
> Sent: Monday, 23 August, 2021 09:22
> We get the SSL_ERROR_SYSCALL from SSL_Read and SSL_Write quite often.
You'll get SSL_ERROR_SYSCALL any time OpenSSL makes a system call (including,
on Windows, a Winsock call) and gets an error.
> It seems the handshake is done
For the below symptoms, I would recommend a watching the application
port with WireShark.
This should show any the TLS protocol deviations and any problems in
handling and establishing the TCP connections.
On 2021-08-19 00:38, David Bowers via openssl-users wrote:
* We have a server that
Hello Michael,
Thank you very much for your detailed response.
We previously had checked the Registry settings for TCPIP Parameters and
have been using the Default values. I also ran the PowershellScript for
the Ephemeral ports and you are correct - the ports are not being exhausted
as it used
> From: openssl-users On Behalf Of David
> Bowers via openssl-users
> Sent: Wednesday, 18 August, 2021 16:38
I don't think this is OpenSSL-related, but at this point it's not clear what
the issue is.
> . After maybe a few hours/days we see the clients dropping connections. The
> logs
>
* We have a server that has around 2025 clients connected at any instant.
* Our application creates a Server /Listener socket that then is converted
into a Secure socket using OpenSSL library. This is compiled and built in a
Windows x64 environment. We also built the OpenSSL for the
