Repository navigation
Massive increase on timeouts after migrating to version 1.5.0 #823
Description
Describe the bug
After migrating from version 1.3.1 to 1.5.0, we've observed a significant increase in timeouts.
This occurs across different endpoints, and we don't have a heavy load on Zendesk servers or any 429 errors. The stack trace below is just one example of numerous calls to different endpoints experiencing this same issue.
java.util.concurrent.TimeoutException: Request timeout to xxxxx.zendesk.com/XXX.XXX.XXX.XXX:443 after 60000 ms at org.asynchttpclient.netty.timeout.TimeoutTimerTask.expire(TimeoutTimerTask.java:45) at org.asynchttpclient.netty.timeout.RequestTimeoutTimerTask.run(RequestTimeoutTimerTask.java:54) at io.netty.util.HashedWheelTimer$HashedWheelTimeout.run(HashedWheelTimer.java:713) at io.netty.util.concurrent.ImmediateExecutor.execute(ImmediateExecutor.java:34) at io.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:701) at io.netty.util.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:787) at io.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:501) at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) Wrapped by: java.util.concurrent.ExecutionException: java.util.concurrent.TimeoutException: Request timeout to xxxxx.zendesk.com/XXX.XXX.XXX.XXX:443 after 60000 ms at java.util.concurrent.CompletableFuture.reportGet(Unknown Source) at java.util.concurrent.CompletableFuture.get(Unknown Source) at org.asynchttpclient.netty.NettyResponseFuture.get(NettyResponseFuture.java:212) at org.zendesk.client.v2.Zendesk.complete(Zendesk.java:3964) Wrapped by: org.zendesk.client.v2.ZendeskException: java.util.concurrent.TimeoutException: Request timeout to xxxxx.zendesk.com/XXX.XXX.XXX.XXX:443 after 60000 ms at org.zendesk.client.v2.Zendesk.complete(Zendesk.java:3982) at org.zendesk.client.v2.Zendesk.getMacro(Zendesk.java:2006)
Activity
[-]Massive increate on timeouts after migrating to version 1.5.0[/-][+]Massive increase on timeouts after migrating to version 1.5.0[/+]PierreBtz commentedon May 18, 2026
@yrdguezro that's quite strange, looking at the 1.5.0 release changes that could impact the timeout I see:
Looking at issues for both of those projects, the most likely culprit would be: AsyncHttpClient/async-http-client#2160 which as a fix linked but unmerged doom369/async-http-client#2.
Let's try to deactivate http/2:
yrdguezro commentedon May 19, 2026
That solved the timouts, thanks
PierreBtz commentedon May 20, 2026
Thanks for the feedback. Closing as there is nothing we can do in this project (won't make this a default since it does not seem to be a widespread issue).