Version 3.16.3: RedisTimeoutException: Command execution timeout for command: (PING)
See original GitHub issueAfter switching to version 3.16.3, I see tons of next exceptions:
org.redisson.client.handler.PingConnectionHandler : Unable to send PING command over channel: [id: 0x76185fba, L:/127.0.0.1:59095 - R:localhost/127.0.0.1:6379]
org.redisson.client.RedisTimeoutException: Command execution timeout for command: (PING), params: [], Redis client: [addr=redis://localhost:6379]
at org.redisson.client.RedisConnection.lambda$async$1(RedisConnection.java:255)
at io.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:669)
at io.netty.util.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:744)
at io.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:469)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:829)
And I don’t see the same in v3.16.2.
Issue Analytics
- State:
- Created 2 years ago
- Comments:15 (8 by maintainers)
Top Results From Across the Web
Command execution timeout for command: (PING) · Issue #4451
My older redisson version is 3.16.7,I tried to upgrade the redisson version to 3.17.0 ,But it can't solve this problem.
Read more >org.redisson.client.handler.PingConnectionHandler$1.run ...
RedisTimeoutException : Command execution timeout for command: (PING), params: [], Redis client: [addr=redis://cruise-redis-master.reddwarf-cache ...
Read more >Redisson/CHANGELOG and Redisson Releases (Page 9)
Fixed - RedisTimeoutException: Command execution timeout for command: (PING) (regression since 3.16.3) Fixed - wrong wait time calculation in ...
Read more >SentinelServersConfig (Redisson 3.7.2 API) - Javadoc.io
Defines PING command sending interval per connection to Redis. T, setPingTimeout(int pingTimeout). Ping timeout used in Node.ping and Node.pingAll operation.
Read more >#rbucket* | Explore Tumblr Posts and Blogs | Tumpik
... RedisTimeoutException: Command execution timeout for command: (PING) (regression since 3.16.3) Fixed – wrong wait time calculation in RedissonMultiLock ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hello, We also face this issue with following complete error and stacktrace :
We are mainly using Queues, locks and MapCache. We are observing this error starts occurring and then our service is producing more and more error logs like the one provided. Is this commit supposed to fix our use case ? Did someone bypassed this issue with specific configuration ? As far as I can see, it’s supposed to be shipped in 3.16.9, but do you have and ETA for that version to be released ?
Than you for your support.
@nladuguie
Next version will be released during this month.