Why are established connections piling up?

Question

go

Good afternoon,
There is a web server on go, why do tcp established connections accumulate during its operation? Moreover, when reaching, say, one hundred such connections, the server simply stops responding to requests.
In which direction should you "dig" to find the cause and fix it?
The load is small. There are no unclosed .Get requests in the code.

Answer 1

established means the connection has been established.
Apparently:
1. It is not closed (in the go code)
2. The connection is really established and so conceived.
About "stops responding", probably the "http listener" is not configured, namely the "backlog" option - the number of processed clients per worker, by the way, if there are enough cores, then you can make more workers.