https://bz.apache.org/bugzilla/show_bug.cgi?id=65631
--- Comment #2 from Pavel Mateja <pa...@verotel.cz> --- Hi Yann, you are right. One of our applications did not close sockets after proxied requests properly. I was able to see long lasting connections in FIN_WAIT2 state but still assigned to Apache's PID. Like tcp 0 0 AB.XYZ.49.8:8080 AB.XXX.48.134:53119 FIN_WAIT2 109016/httpd instead of just tcp 0 0 AB.XYZ.49.8:8080 AB.XXX.48.134:1916 FIN_WAIT2 - In such case kernel won't clean them up. I can see AH10212: proxy: CONNECT: tunnel running (timeout -1.000000) in debug log. Which configuration parameter sets this timeout nowadays? ProxyTimeout did not do the trick. This was just fixed on application side and such connections are no more. But those 500 in logs are still present. I've tried older Apache versions and I don't see them with 2.4.46. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org For additional commands, e-mail: bugs-h...@httpd.apache.org
