Does Gatling Close Both the Application Connection and the Database Connection When maxDuration is Exceeded or the request triggered by Gatling is TimedOut

General discussions
1

Does Gatling Close Both the Application Connection and the Database Connection When maxDuration is Exceeded or the request triggered by Gatling is TimedOut?

Hi everyone,

I have a question regarding how Gatling handles request timeouts when the maxDuration is exceeded.

Scenario:

  • We have a Spring Boot application that exposes APIs, which internally call a Microsoft SQL Server stored procedure via JDBC (HikariCP).
  • The API request triggered by Gatling can take a long time to complete due to the database processing.
  • In Gatling, we have set a maxDuration, and when this duration is exceeded, Gatling times out the request.

Question:

When Gatling times out a request due to maxDuration, does it:

  1. Only close the HTTP connection between Gatling and the application (Spring Boot)?
  2. Or it Also signal the application server to stop the ongoing database query (i.e., does it cause Spring Boot to cancel the JDBC call and terminate the stored procedure execution in SQL Server)?

Is there any documented behavior on how Gatling handles connection closures in such cases?

Does Gatling Close Both the Application Connection and the Database Connection When maxDuration is Exceeded or the request is TimedOut? Or Does Gatling close only the Application Connection while the Triggered Database Proc still continues to execute.

Is there any documented behavior on how Gatling handles connection closures or request timeOut in such cases?

2

That’s not a question for Gatling but for Spring Boot.

On request timeout, Gatling closes the HTTP connection. What happens on the server side then purely depends on your application. In the case of Spring, I expect that nothing happens and that the application thread continue its execution until it fails to write the response on the socket.

3

Thanks for the revert, Would check further on it.