Getting HTTP/2 GOAWAY's when consuming the API

Web API
#1

Hi, we are experiencing an issue when consuming the REST API: sometimes, our client gets a HTTP/2 GOAWAY frame when issuing a request.

What could be the reasons for this?

Do you maybe have some kind of rate-limiting in place that uses GOAWAY to signal over-usage?

We are using Java’s (JDK 21) HttpClient, which keeps an internal pool of connections (30 sec. idle timeout, 100 max. concurrent HTTP/2 streams), just in case this is relevant.

Thanks.

#2

Dear @Mingbo,

Thank you for reaching out!

It is likely an issue with your Java client and is not caused by us.

#3

We noticed GOAWAY errors started to appear after 1 hour. We have then setup our client code so that it pools connections up to 30 min. max.

We are since no longer getting the error, so it seems this was indeed a pooling related issue.

Thanks