×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I'm encounterring a problem that I couldn't quite understand. The
problem is related to closing the socket connection and then reconnect
again. When I attempt to reconnect, I'll, sometime, get the "A remote
host refused an attempted connect operation." error. It almost seems
like the close didn't really drop the connection on the server side and
make the server port become available again.
I did some googling and found this:
When the close() system call is initiated by an application, only the
interface to the socket is destroyed, not the socket itself. It is the
kernel's responsibility to destroy the socket internally. Sometimes, a
socket may enter a TIME_WAIT state, on the server side, for up to 4
minutes.
Would what I found above be the cause of my reconnect problem?
Thanks
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.