PrematureCloseException with SQS requests after upgrading to Gatling 3.15.0

augustelaa
Wed, 18 Mar 2026 08:22:49 +0000
Gatling (Open-Source)

Gatling version: 3.15.0
Gatling flavor: java kotlin scala javascript typescript
Gatling build tool: maven gradle sbt bundle npm

Hi everyone,

After upgrading our project to Gatling 3.15.0 (using the io.gatling.gradle plugin), our performance tests started failing with the following exception:

i.g.h.c.i.PrematureCloseException: Premature close

This happens on all requests made to the AWS SQS Query API.

Example request:

exec(
  http("My Request")
    .get(queueUrl)
    .queryParam("Action", "GetQueueAttributes")
    .queryParam("AttributeName", "ApproximateNumberOfMessages")
    .sign((request, _) => mySignManager.sign(request))
    .check(status is 200)
)

The failing requests look like:

GET https://sqs.eu-west-1.amazonaws.com/9999/my-queue
?Action=GetQueueAttributes
&AttributeName=ApproximateNumberOfMessages

What’s interesting is that rolling back the plugin from 3.15.0 to 3.14.9.8 makes the problem disappear, without any other code changes.

So it seems related to something introduced in Gatling 3.15.0 (possibly an HTTP client or Netty upgrade?).

Has anyone else experienced similar issues with PrematureCloseException after upgrading to 3.15?

Thanks!

15 posts - 3 participants