Test execution gets stuck after starting TLS server

[nilshenrich]

In some gtest executions, the runtime gets stuck right after starting TLS server, see:

[nilshenrich]

There is no CPU load and the memory usage doesn't grow

[nilshenrich]

The test execution gets stuck in TlsClient::start method

[nilshenrich]

The test execution gets stuck in TlsClient::start method

Stuck at TlsClient::connectionInit method

[nilshenrich]

The test execution gets stuck in TlsClient::start method

Stuck at TlsClient::connectionInit method

Stuck at TLS handshake: SSL_connect

[nilshenrich]

Possible solution: timeout to don't get stuck infinitely. ChatGPT generated solution:

struct timeval timeout;
timeout.tv_sec = 5;  // Timeout in seconds
timeout.tv_usec = 0;

setsockopt(sock, SOL_SOCKET, SO_RCVTIMEO, &timeout, sizeof(timeout));
setsockopt(sock, SOL_SOCKET, SO_SNDTIMEO, &timeout, sizeof(timeout));

[nilshenrich]

Possible solution: timeout to don't get stuck infinitely. ChatGPT generated solution:

struct timeval timeout;
timeout.tv_sec = 5;  // Timeout in seconds
timeout.tv_usec = 0;

setsockopt(sock, SOL_SOCKET, SO_RCVTIMEO, &timeout, sizeof(timeout));
setsockopt(sock, SOL_SOCKET, SO_SNDTIMEO, &timeout, sizeof(timeout));

No, SO_RCVTIMEO and SO_SNDTIMEO just define the timeout for sending/receiving data on TCP socket

[nilshenrich]

Solution could be:

1. Start a timeout counter in background just before calling SSL_connect. If timeout has passed without SSL_connect having returned, abort it by freeing the TLS socket: SSL_free
2. Use non-blocking mode just for connecting and keep trying until timeout has passed