| Dart Home | PowerTCP WebServer for ActiveX | Custom Development | Reply | PowerTCP WebServer for ActiveX Topics | Forums |
| Author | Forum: PowerTCP WebServer for ActiveX Topic: Sockets remaining open |
| chris@digitalinsights.com From: San Clemente, CA USA Posts: 73 Member Since: 11/03/03 |
posted September 7, 2005 12:47 PM I have a situation where the webserver controls stops working and freezes the program it is in. When you kill the process and then do a netstat -a -n, you have several hundred sockets still open in either Established or Waiting mode. How can these stick around even when the process is gone? Thanks |
| chris@digitalinsights.com From: San Clemente, CA USA Posts: 73 Member Since: 11/03/03 |
posted September 7, 2005 12:53 PM I know I posted something like this about a year ago. I have never had a concrete solution to it so I am asking again to see if any new has occurred. |
Tony Priest From: Utica, NY USA Posts: 8466 Member Since: 04/11/00 |
posted September 7, 2005 1:03 PM I'm not really sure how that could happen. If you figure out a way to duplicate the issue using our sample app, please email support@dart.com with the steps. Thanks. |
| chris@digitalinsights.com From: San Clemente, CA USA Posts: 73 Member Since: 11/03/03 |
posted April 26, 2006 2:58 AM I know this is old, but it keeps dragging down machines. The issue is that if you connect to the server with a browser like IE, and request a document, the socket/port stay ESTABLISHED until after a long period, or you close the browser. I need to have the socket/port close immediately after the request is fulfulled because with the amount of activity going on the machine gets overwelmed with these open ports. |
| chris@digitalinsights.com From: San Clemente, CA USA Posts: 73 Member Since: 11/03/03 |
posted June 6, 2006 5:32 PM Ok, I used your webserver sample application, started it, using IE was able to open a page. I used TCPView to notice that while the browser was open, the connection to port 80 stayed ESTABLISHED. When I close the browser, the connection went away. BUT, if I put a hyperlink in an email, send it to myself using Outlook, then read it with outlook and click on the link (ie: http://127.0.0.1), the page comes up fine, I close the browser, the ESTABLISHED connection does not go away. I close Outlook, the ESTABLISHED connection does not go away. I close the webserver sample app, the ESTABLISHED connection now goes away. Please explain. |
| Tony Priest From: Utica, NY USA Posts: 8466 Member Since: 04/11/00 |
posted June 6, 2006 7:33 PM It's probably Keep-Alive. Check your IE advanced settings under HTTP 1.1 options and you should see an option for disabling Keep-Alive. |
| chris@digitalinsights.com From: San Clemente, CA USA Posts: 73 Member Since: 11/03/03 |
posted June 6, 2006 7:51 PM There is not keep alive setting on my IE v6. But even so, I wont be able to have clients change it. Is there a way to make the webserver control just serve up the file requested and just disconnect? |
| chris@digitalinsights.com From: San Clemente, CA USA Posts: 73 Member Since: 11/03/03 |
posted June 6, 2006 7:55 PM Or, is there a way to change the request header so that the Connection parameter could be changed to close? The think the request object is read-only though... |
| Tony Priest From: Utica, NY USA Posts: 8466 Member Since: 04/11/00 |
posted June 6, 2006 8:04 PM You can change the Response.Header's parameter's. I believe that the line would be: Connection: close Try that and let me know if it works. |
| chris@digitalinsights.com From: San Clemente, CA USA Posts: 73 Member Since: 11/03/03 |
posted June 6, 2006 8:28 PM I am doing the Response object connection:close thing now, and it does help a little, but the effect is still awkward. By sending that response to the browser, it causes the browser to close the connection but it puts the connection on the server into a TIME_WAIT that can still stay around for up to 4 minutes, and in a high traffic environment, it hits a critical limit quickly. The best thing would be to have a setting that would "force-close" (ignore keep alive in header) settting. |
| Tony Priest From: Utica, NY USA Posts: 8466 Member Since: 04/11/00 |
posted June 6, 2006 8:32 PM Unfortunately that's the best I can offer with the existing product. If you feel that the ability to close the connection immediately is important enough to warrant the addition of a new feature, please email David Harry (sales@dart.com) to discuss options. |
| Reply | PowerTCP WebServer for ActiveX Topics | Forums |
This site is powered by
PowerTCP WebServer for ActiveX
|