Migration Guide 3.31

Table of Contents

• Agroal/JDBC
• Load Shedding
• Testcontainers
• Removed deprecated Amazon Lambda Testing module

Note	We highly recommend the use of quarkus update to update to a new version of Quarkus. Items marked below with ⚙️ ✅ are automatically handled by quarkus update.

Agroal/JDBC

The default maximum size of the JDBC connection pool has been raised from 20 to 50, to be more in line with modern standards.

If you relied on the default to be 20 (for instance, if you set the maximum connections to 20 on the database side), make sure to adapt your configuration or infrastructure.

Load Shedding

Previously, the load shedding extension didn’t document what types are passed to RequestClassifier and RequestPrioritizer. The type used for HTTP requests was io.vertx.core.http.HttpServerRequest.

In this release, this changes. The used type is now io.vertx.ext.web.RoutingContext and it is documented in both RequestClassifier and RequestPrioritizer.

Testcontainers

Testcontainers has been updated to Testcontainers 2.0. Some artifacts have been renamed together with package names so you might have to adjust your applications if you are using Testcontainers directly.

Removed deprecated Amazon Lambda Testing module

The Amazon Lambda Testing module quarkus-test-amazon-lambda and the io.quarkus.amazon.lambda.test.LambdaClient, which has been deprecated in Quarkus 2.3.0, have now been removed from Quarkus. If you are still using this method to test Amazon Lambdas, please move to using RestAssured instead: https://quarkus.io/guides/aws-lambda#live-coding-and-unitintegration-testing.