<p>I currently load testing my service using Gatling in AWS. I did several load tests using HTTP and my service works perfectly. No TLS handshake errors. When we moved to the HTTPS, the load test result showed <strong>TLS handshake timeout</strong> exception all over the place and finally thrown OOM because unprocessed request getting queued.</p>

<p>Additional information: </p>

<ul>
<li>The Gatling scenario will be like this:
Sends three requests and send one request with the <code>connection: close</code> header. I wanted to simulate sending three requests that is kept alive and close it at the end. </li>
<li>My service is managed by Kubernetes. </li>
</ul>

<p>What I have done:</p>

<ul>
<li>I ran the load test on other Gatling instance, but the error still persists </li>
<li>Restarted the AWS load balancer. Additional notes: There are no 4xx and 5xx errors, but we have client TLS negotiation errors.</li>
</ul>

<p>My questions:</p>

<ol>
<li>Is the error occurred because of the initial handshake required for the HTTPS? </li>
<li>Is the error occurred because of the AWS load balancer?</li>
</ol>

<p>Thank you. </p>

<p>So it seems the problem was because the time it took for Gatling to handshake longer than the creation users per second. By decreasing the number of users created and increasing the number RPS solved that.</p>
