I want to understand the working of request Timeout configuration present in gatling.conf file.
Case : Only using requestTimeout field in ahc settings
So, basically if a request times out , does gatling end that http connection and a new one is formed or that connection stays but another http connection is also generated ?
Basically, in my tests , when I am receiving the these timeouts, http gatling connections are not ending , rather increasing in accordance with the users.
How can this be handled?
And can any other ahc settings field help to solve this situation ?
Can someone help me understand this all better ?