Hey there,
We observed that the Web Service\Current Connections counter for one of our ISAPI Filter keeps increasing in production, and eventually (when the value reaches around 270000) the incoming traffic will be “rejected” by getting 500 internal server errors.
Our ISAPI Filter does the following things 1. For normal request, we send 302 response back and return SF_STATUS_REQ_FINISHED_KEEP_CONN 2. For http (port 80) and https (port 443) calls to access one of our .js file, we return SF_STATUS_REQ_NEXT_NOTIFICATION but don’t send response…
The protocol is HTTP/1.1 and it’s IIS 6.0 on our server machines.
On IIS, we have the connection timeout of 2 second and have the Keep-Alive disabled
So the questions here are –
why the Current Connections keeps increasing?
Is there any other settings in IIS (6.0) that may impact/change the behavior?
Could it be the ssl (https) calls that keep the connection open without close them?
For the 2nd category of calls above, does it required to have connection : close in the requests header in order to have the connection closed?
Can anyone please help?
Thanks, Tom