CSM use TCP FIN or RST For keepalives

[jrcooper]

Currently the version if WebNS we have deployed on our CSS11800 use a TCP RST to close the TCP connection that is established for TCP Keepalives. This can be a problem when the server is a weblogic server. Therefore we run a scripted keeplive that uses a TCP FIN.

I am wondering if the CSM uses a TCP FIN or RST to close the TCP connection that is established for TCP keepalives. Can anyone help?

[Gilles Dufour]

The same.

Inside script you can use either RST or FIN.

The default is RST but you can change it to FIN.

However, the reason for the RST is that it frees the TCP socket immediately without waiting for the server response.

If you have to wait, you held the resources which are limited.

And if your number of KAL increases, you could run into trouble.

So, use with care.

Gilles.

[jrcooper]

Excellent, thank you.

I understand why it would use an TCP RST as opposed to a TCP FIN, but if you use a TCP RST with WebLogic servers it causes them to hang. Therefore the TCP connections need to be closed "gracefully" using a TCP FIN.

I know new versions of WebNS let you configure if the Canned TCP Keepalives use a TCP FIN or RST. I guess I will have to use a script on the CSM to close the TCP keepalive.

Once again Thanks.