Thanks Mark, Will have a look to enable debug mode. Probably need to do some investigation as Tomcat is embedded in the full product and some probably some standard logging configuration is changed.
Tom On Wed, May 22, 2019 at 5:01 PM Mark Thomas <ma...@apache.org> wrote: > On 22/05/2019 15:47, Tom Coudyzer wrote: > > Hi, > > > > We wanted to upgrade our application to start using HTTP/2. We added the > > necessary and we see that the browser is using HTTP/2 in the browsers' > > development tools. > > > > However since we activated it we get random CONNECTION_CLOSED 200 Errors > in > > Chrome. It's not always on the same files and sometimes there are more, > > sometimes there are less, sometimes it works. When we disable HTTP/2 > > (remove the upgradeprotocol tag) everything works fine. > > > > We are running Tomcat 9.0.20 (x64) on a Windows Server 2008 R2 server. > > > > Did we configure something incorrectly, is this an HTTP/2 issue or should > > we look at network issues on our end? > > > > If you need more information or we need to run something to be able to > > troubleshoot it better please let me know. > > > > Help is much appreciated ! > > You can try enabling debug logging if the issue is fairly easy to > reproduce. That might shed some light on what Tomcat is doing and why. > > There are also some HTTP/2 fixes due in the next set of releases that > might help. > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
