-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
All thread was blocked #634
Comments
If you captured a thread dump (jstack) then we might be able to find the cause. We would need to know which thread holds the lock and why. You can email that privately. The usual suspects are,
I am not aware of any library bug at this time, so my initial guess leans towards application or Linux issues as we've encountered them as the causes in the past. But we need more details to determine the root cause regardless. |
Another case is recursion causing a stack overflow that failed to release the lock. See #203 (comment). JEP-270 tried to handle this but it may not be full proof. |
Closing due to lack of response. Please reopen if I can be of help. |
os: ubuntu-18.04.6-live-server-amd64 2core 4G
jdk: 11.0.11+9-Ubuntu-0ubuntu2.18.04
caffeine version: 2.9.3
return Caffeine.newBuilder() .scheduler(Scheduler.forScheduledExecutorService(Tasks.scheduler()));
server qps: 5500+
5 client threads access cache that everything is ok, but when 10 client threads access cache that everything seems frozen.
Plz help, thx.
The text was updated successfully, but these errors were encountered: