A pooled HTTP connection reused after an idle lull

A service calls a backend over HTTP/1.1 through a client-side connection pool that keeps idle connections for up to 60 seconds. The backend's HTTP server closes keep-alive connections that have been idle for 5 seconds. Both hosts sit in the same subnet with no proxy or NAT between them. Intermittently, a request fails immediately with ECONNRESET or an empty response, and it is almost always the first request after a lull of more than 5 seconds. What is happening?

39 of 45 in Networking