It looks like I have an end user who's TCP stack is not working correctly: immediately after sending his initial HTTP GET, he sends an ACK for a packet I haven't sent yet. I send the proper sequence number on the reply but he's stuck on the wrong one and away we go with an ACK storm that lasts thousands of packets on multiple streams.
I'm amazed that nothing in the path kills the session... I have an ASA w/IPS and a CSS fronting WebLogic web servers and none of them do anything except reply like mad.
I'm hunting for a way to stop these things from dragging down performance but I don't see anything yet... suggestions?
Thanks - Al