smallrye-context-propagation | SmallRye implementation of MicroProfile Context Propagation | Graph Database library

I have a Quarkus project that expose some REST Endpoints. When working on dev mode or running from the local build docker container all work fine, those endpoints annotated with @RolesAllowed and @PermitAll work as supposed to be. But when I deploy to a AWS service with the following steps:

1. Commit to Gitlab
2. Run Gitlab CICD
3. Send result with the config to an AWS S3 Bucket
4. Trigger AWS codepipeline
5. Deploy to Elastic Bean using docker image

After that the container is deployed all endpoints with @PermitAll work fine but those with @RolesAllowed responds with 401 Unauthorized, the token sent to those endpoints is valid, it is correctly formed and has not expired.

I'm trying to use Quarkus and JDBI — not so many examples on this out there I would say :/

The Gradle script has these dependencies:

I started a project and have about 7 tests in my project now and it takes already more than a minute to execute the whole test suite using gradle test.

From the additional output (--info flag) I can see that the whole quarkus application and also dependencies like the mongodb instance are restarted for every test class and method.

This is the exact opposite of what the quarkus documentation says on the testing guide page:

So far in all our examples we only start Quarkus once for all tests. Before the first test is run Quarkus will boot, then all tests will run, then Quarkus will shutdown at the end. This makes for a very fast testing experience however it is a bit limited as you can’t test different configurations.

All the tests are annotated with @QuarkusTest and every test just tests a single endpoint.

I use "pure" kotlin (1.5.21), Quarkus version 2.2.2.Final and gradle 6.9. Installed features: cdi, config-yaml, jacoco, kotlin, mongodb-client, mongodb-panache-kotlin, narayana-jta, rest-client, rest-client-jackson, resteasy, resteasy-jackson, smallrye-context-propagation, smallrye-health, smallrye-openapi, swagger-ui

Is that a normal behaviour? If yes, an application with multiple hundred tests could easily take ~20 minutes or more to run the entire test suite.

I didn't try out maven yet, so I can't verify that it's not a gradle related issue.

I created a simple quarkus lambda rest project as described in the documentation

All my applications written in Quarkus/Java can't be accessed in localhost:8000 exposed in dev mode when running inside WSL 2.

From my project's root directory, I issued the following command to create a native executable that will be specific to my operating system. See the following guide for details

I created a new Quarkus app using the following command:

Warning message

WARN [io.qua.hib.orm.dep.HibernateOrmProcessor] Could not find a suitable persistence unit for model classes:
- io.quarkus.hibernate.orm.panache.kotlin.PanacheEntity
- io.quarkus.hibernate.orm.panache.kotlin.PanacheEntityBase

The same issue with both io.quarkus:quarkus-hibernate-orm-panache and io.quarkus:quarkus-hibernate-orm-panache-kotlin (PanacheCompanion).

My project has multiple named persistent units and datasources (no default). I'm also using multitenant feature.

INFO [io.quarkus] Installed features: [agroal, cache, cdi, config-yaml, hibernate-orm, hibernate-orm-panache-kotlin, jdbc-mysql, kotlin, mutiny, narayana-jta, resteasy, resteasy-jackson, security, smallrye-context-propagation, smallrye-jwt, smallrye-openapi, swagger-ui, vertx, vertx-web]

I have created a test project where I have combined two guides: Quarkus-DynamoDB and Quarkus-HTTP lambda. The end goal of this was to have an example project where a lambda communicates with DynamoDB, and this is all compiled natively (using GraalVM).

This has worked relatively well. I managed to deploy the project to AWS lambda using the tools from the second guide, and the responses I get when calling the endpoints are as expected.

However, I have some questions about the performance, particularly after a startup.

When hitting the simple "hello" endpoint from the first guide, the times look like this: