Re: Socket close() and then re connect()

One situation where this might happen is where you are connecting to load-balanced set of servers, and one or more of them is not responding - possibly due to a crash on that system. This can result in intermittent failure. l would call the partner's support center before putting any more into diagnosis.

"Lim Hock-Chai" <Lim.Hock-Chai@xxxxxxxxxxxxxxx> wrote:

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



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.