Hi, Lukas! > Like I said, you will need to reproduce the problem on a box with > no traffic at all - so the impact of a single connection can be analyzed > (sockets status on the frontend/backend, for example). > > Its nearly impossible to this on a busy box with a lot of production traffic. > > Also, the configuration needs to be trimmed down to a single, specific use > case (you already said you suspect a specific backend).
I follow your idea, but it seems single connection couldn't reproduce the problem. The sockets stats disappeared very fast when I open my explorer.And I analyzed with wireshark and didn't see any abnormal flows or packets.
