Hello, we’re using haproxy since version 1.7 for our websites. Backends are mostly Apache Tomcat. We have a centralised log server for application logs. A couple weeks ago we upgraded to 1.8.13 and enabled h2. Since then, in our logging system we started to see a number of 500 responses. What’s strange is that users didn't notice any issue and “near” a 500 response there’s almost always a 200 response for the same URL. Looking further into the problem we found that 500s are caused by what java reports as IOException for ‘Broken Pipe’. We find such errors for a number of client user-agents so it seems not “client” related or at least if it’s a client problem it’s widespread.
Is this a problem that can be related to how haproxy works with the h2 protocol ? Is it possibile that for some reason it’s haproxy that is calling the same url two times and one of the connection is then interrupted ? Thank you -- Ing. Andrea Vettori Responsabile Sistemi Informativi
