On Mon, 10 Dec 2007 15:35:08 -0600, Cynthia Davis
<[EMAIL PROTECTED]> wrote:
>... When I look at the Maximum in backlog I show
>many different numbers other than the 1500. Last week a DB2
application
>which is showing maximum in Backlog of 50, exceeded this by 2 so
those 2
>connections were dropped due to backlog exceeded. Today we have
28
>connections dropped for our FTPD1 application. The maximum backlog
for
>FTPD1 is showing 50 as well. Can anyone tell me where I change the
>Maximum in backlog for FTPD1 and DB2 applications?
>...
The backlog queue length can be set when opening a socket.
I can find no way of setting it for the FTP daemon. If that capability
is available it does not have "backlog" in its description.
I think I remember hearing our DB2 guru mentioning setting it. but
I know nothing about DB2 so I'm no help there.
Before changing the backlog limit, consider the effect. You replace
unexpectedly dropped connections with unexpectedly hung ones.
Whether remote end is a person or a program, more information is
available to the remote for the dropped connection ("Reset by
Remote") than for the hung connection (No information whatsoever.)
Pat O'Keefe
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
