> If the server stop completely, I see two possibilities:
> 1) The server is stopped (the socket server listening for connections is
> closed). This may happend when you have a bug and unexpectedly close a bad
> [file or other] handle. If it happends that the wrong handle is the
> listening socket handle, no other connection will be accepted.
> (CloseHandle() applyed to a socket handle will close the socket).
> 2) The thread servicing the HTTP server is blocked and doesn't call the
> message pump anymore. So no event is triggered nor handled and nothing
> happend any more regarding socket I/O which - as you know - is event
> driven.OK, you shall tell you that my answerstring is between a trI found it,
> it was the first possibilities : a bug. We are in a 3 tier application so we
> have to manage the refresh of our dataset but one of the refresh procedure
> where bugged (a bad copy/paste or, in french, "un copier/coller assassin")
> and raise an uncaught exception....By the way I've seen it not thanks to my
> log files but with Windows Event Manager. It log uncaught exception on my
> service, this help me beacause the time of each log correspond to my refresh
> time....T_Tthanks sincerely,PS: I haven't receive messages in my mail box so
> I'd to create new message and so new thread. For all users, I
> apologize.--------------------------------------Guillaume ROQUESCANYON
> Technologies
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
