On Thu, 2020-05-14 at 10:53 +0200, u...@natune.net.INVALID wrote: > > > While using HTTP/2 only client, after approx. 12 hours the > > > connection > > > is > > > broken and is not established anymore. Every couple of minutes > > > async > > > HTTP/2 requests are sent to a Tomcat9 server. There are no errors > > > whatsoever but after a couple of hours every request fails until > > > the > > > application running HttpClient 5.0 is restarted. > > > > > > Would an evictIdleConnections() call help in this case? > > > Let's suppose Tomcat would close the connection after some time, > > > what > > > is > > > Httclient 5.0's default reaction? Is it re-established > > > transparently? > > > > > > > Yes, it should, I am afraid I would either need a reproducer or a > > full > > execution log of the session that exhibits the problem. > > > I haven't had the chance yet to enable full logging yet, but after > the > first "Connection closed" Exception, and a couple of requests going > through, the cause for failed connection establishment is an "I/O > reactor has been shut down" Exception. That's what I could find out > up > to now. >
I need to see the original exception with a full stack trace that caused the i/o reactor to shut down and preferably the complete session log leading to that condition. Oleg > > br, > > Can > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: httpclient-users-unsubscr...@hc.apache.org > For additional commands, e-mail: httpclient-users-h...@hc.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: httpclient-users-unsubscr...@hc.apache.org For additional commands, e-mail: httpclient-users-h...@hc.apache.org
