I previously posted:
I have a process that listens on a port and for which discarding excess
connection requests is the desired behaviour. Unfortunately, connection
requests getting discarded generates warning messages of the form:
sonewconn: pcb {address}: Listen queue overflow: {#} already in queue
awaiting acceptance ({#} occurrences)
Is there a way for the process or some config file to request
suppression of these warnings in regard to that process?
Lowell Gilbert <
lgusenet@be-well.ilk.org> kindly replied:
Not a direct answer, but I prefer to close the listening socket for
these cases. I find it makes for more understandable behaviour from the client's point of view.
Hi, Lowell. Glad to see you're still here.
I think you're suggesting that when the process reaches its desired
connection limit, it should close the listen port, and then reopen it
again when its willing to accept more.
Two alternatives come to mind, and perhaps you can tell me which you
have in mind and what happens in case 2.
1) If I continue to specify a connection limit of N and N+5 requests
come in too quickly, even if I close the listen port upon reaching N
active connections, it seems to me that excess requests could arrive
before the port gets closed, thus generating sonewconn warnings.
2) If I don't specify a connection limit and close the listen port upon
reaching N active connections, do the excess connections just get
closed? (So then instead of being rejected, they get connected and
closed.) Obviously that's only better if doing that doesn't generate
its own warning messages about closing a port while there are
requests pending. :)
Yeah, part of this is me griping that an O/S shouldn't issue warnings of
the form "This is to let you know I'm doing what you requested" unless debugging has been enabled. :-/
-WBE
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)