-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Quarkus initializing VertX cache even with vertx caching disabled #28094
Comments
/cc @gwenneg |
Any chance you can provide a sample project that reproduces this issue? |
I normally link a reproducer but in this case I don't know how to provide one as ECS is not included in AWS free tier. Required to reproduce the exact problem: ECS service running one task where
Will try if I can reproduce it locally, so I can maybe provide a reproducer. |
I think that if you have a reproducer, we can make things fail locally by tweaking the cache directory location |
Demonstrator (default generated project from code.quarkus.io and added quarkus.vertx.caching=false to app properties): https://github.com/syr/code-with-quarkus Reproduce by
stacktrace
|
To overcome your problem you essentially also need to set #28142 will take care of the warning messages you see in the output. |
Prevent attempt to create Vert.x caching dir caching is disabled
Closes: quarkusio#28094 (cherry picked from commit 2652931)
Same issue now with latest Quarkus 2.13.3.Final, when using quarkus-smallrye-graphql-client
I get error
Maybe graphql client does not work without vertx cache or it is missing to respect
Reproucer based on microprofile-graphql-client-quickstart: https://github.com/syr/code-with-quarkus Not sure if this issue should be reopened or if I should create another one. |
Please create a new one |
To comply to AWS ECS security rules we want to enforce read only filesystem access (https://docs.aws.amazon.com/config/latest/developerguide/ecs-containers-readonly-access.html)
This requires that vertx caching is disabled. However, no matter if defined by env var
QUARKUS_VERTX_CACHING=false
or app property:
quarkus.vertx.caching=false
eventually, vertx caching is still active, causing the application to crash on startup
The text was updated successfully, but these errors were encountered: