Forum Discussion
Capturing TCP resets (part deux)
Click here
I found this post about catching TCP RST, and was wondering if we can do more now, and also hoping to find out more about connection management behaviour with OneConnect.
1) Has anything like "IP::payload" or "TCP::flags" been added since then?
2) If the server sends a RST on a OneConnect connection, does it trigger SERVER_CLOSED? CLIENT_CLOSED? I'm assuming the server side connection is closed and re-opened?
thanks!
/deb
- JRahm
Admin
Did you get an offline answer to this deb? We are having an issue where we're trying to correlate apache 502 responses to the clients to errors in our application tier, and have been unable to do so. - No, sorry -- I'm still in the dark on this one.
Something like [IP::payload] would sure come in handy for a number of things I've touched recently, though.
I suppose I should see if there's a CR for that yet, and open one if not...
/deb - Sorry, no is the answer for 1).
As for 2), yes I would expect SERVER_CLOSED to get triggered. Also, I believe that the RST is propagated to any currently connected client, so I would expect CLIENT_CLOSED to get triggered if there's actually a client connected at the time of the RST.
