Intrafoundation Software
Making Atomic Warfare Fun Again
News & Forums Active Projects Queued Projects | War & Politics God Cryptography Operating Systems Game Development | Writings Poetry Film Making Wisdom | ColdFusion ASP COM Objects Javascript Web Design Java | Photography Raytracing DOS Software

| Need a shoulder to cry on while trying to convince Windows to properly work with our software? Just want to chat about something related to the site? Feel free to use the forums slash news slash blog. (Unsolicited commercial spam will be deleted, obviously.) | Looking for something?

This is thread 121. The complete list of threads is available on the main forums page.

Subject: Telnet connection not fully closing Author: Rob McClain Date/Time: 9/20/2002 3:55:30 PM (121.0) Greetings, I am having a problem with the TCPClient. I am using a ColdFusion server running under Windows 2000 to telnet to a UNIX system. The problem occurs when the connection should be closed. When I run netstat on the CF server, the socket is in the CLOSE_WAIT status. On the UNIX system, netstat reports the socket is in FIN_WAIT_2. This indicates to me that the TCPClient needs to send an ACK to the UNIX system to complete the connection breakdown. Eventually, there are enough "dead" sockets to bring the TCP stack on the CF server to a halt. The CF page I am using is processed every minute by the CF scheduler. On each load, it alternates between opening 1 of 2 TCPClient objects (created as application variables) and closing the other (with Close() ). The telnet session only consists of logging in, the remainder is in the .profile (ending in exit to close the session), and is completed before the next scheduled page load. Any suggestions on how to avoid or eliminate the "dead" sockets would be much appreciated. Thank you, Rob McClain mrm@thor.co.alachua.fl.us

| REPLY
--- | ---
Author: |
Subject: |
Your Message: |
Email: (optional) |

`(Note: For safety all HTML in your message text may be printed exactly as you typed it.)`
top