This document provides information for graceful close on Content Switching Module (CSM) probes.
The BEA™ Weblogic server (BEA) runs out of resources, and cannot handle a Reset (RST) flag on the probes. The CSM runs out of resources and cannot use the Finish (FIN) flag on the probes. Unless either BEA or CSM are redesigned, there is no resolution for this issue.
There are no specific requirements for this document.
The information in this document is based on these software and hardware versions:
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
This document can also be used with these hardware and software versions:
For more information on document conventions, refer to the Cisco Technical Tips Conventions.
The CSM supports two types of probe:
Internal probe — these are compiled in code that sends the RST for the TCP probe. The user cannot change this behavior.
Scripted probe — these are Toolkit Command Language (TCL) scripts written by the user. The user specifies the external script file to be downloaded into the CSM. Beginning with CSM release 3.1(3), the user can modify these script probes to send the FIN instead of RST.
The cautionary note is that these probes (using FIN) would put the sockets into TIMEWAIT status, which uses up CSM resources if the probe rate is too fast. The reason for this change is due the limited socket resource on CSM's OS platform. There are only 250 sockets that can be opened simultaneously on the CSM. You can close the sockets with reset to:
By default, the probes sent from the CSM close with a RST; this is not changed due to how the CSM uses resources. The CSM runs out fast with a FIN. You instead need to use a modified TCL script to send a FIN, but you run the risk of running out of socket resources.