Describe the bug
When using CacheResult annotation on method performing several calls to SpringData repository the program is stuck.
Expected behavior
Everything works smoothly
Actual behavior
All threads are in Waiting state (dump)
To Reproduce
Steps to reproduce the behavior:
Configuration
#---data
quarkus.datasource.url=jdbc:postgresql://[my-rds]
quarkus.datasource.driver=org.postgresql.Driver
quarkus.datasource.username=[user]
quarkus.datasource.password=[password]
quarkus.datasource.max-size=200
quarkus.datasource.min-size=10
quarkus.datasource.validation-query-sql=select 1;
quarkus.hibernate-orm.database.generation=update
#---native
quarkus.ssl.native = true
quarkus.swagger-ui.always-include=true
#---security
smallrye.jwt.path.groups=cognito:groups
mp.jwt.verify.publickey.location=[my cognito location]
mp.jwt.verify.issuer=[my cognito issuer]
quarkus.smallrye-jwt.enabled=true
#---CORS
quarkus.http.cors=true
quarkus.http.cors.origins=[origin]
quarkus.http.cors.methods=GET,PUT,POST,OPTIONS
quarkus.http.cors.headers=accept,authorization,content-type,x-requested-with
quarkus.http.cors.exposed-headers=Content-Disposition
quarkus.http.cors.access-control-max-age=24H
#----logs
quarkus.log.level=INFO
#----logs
quarkus.cache.caffeine.test-owner-chain.initial-capacity=10
Environment (please complete the following information):
uname -a : Darwin Eduards-MacBook-Pro.local 19.0.0 Darwin Kernel Version 19.0.0: Thu Oct 17 16:17:15 PDT 2019; root:xnu-6153.41.3~29/RELEASE_X86_64 x86_64java -version: openjdk version "1.8.0_242"
OpenJDK Runtime Environment (build 1.8.0_242-b06)
OpenJDK 64-Bit GraalVM CE 19.3.1 (build 25.242-b06-jvmci-19.3-b07, mixed mode)Apache Maven 3.6.2 (40f52333136460af0dc0d7232c0dc0bcf0d9e117; 2019-08-27T18:06:16+03:00)/cc @geoand
Thanks for reporting this.
I was not able to reproduce the problem unfortunately. Would you be able to supply a minimal reproducer containing only the Spring Data JPA and cache stuff that exhibits the problematic behavior?
I will try.
/cc @gwenneg
This probably shares the same root cause than #13158.
There's a good chance this issue was fixed with #13244.
Feel free to reopen if that's not the case.