Re: TCP/IP COMMUNICATIONS FAILURE
1997-01-13 07:59:13
Subject: |
Re: TCP/IP COMMUNICATIONS FAILURE |
From: |
"CN=U0782/O=SDC@SDC @ SDC_EXTERN_DOMAIN U0782 - DKSDCPLN" <dksdcamc AT IBMMAIL DOT COM> |
Date: |
Mon, 13 Jan 1997 07:59:13 EST |
==============================================================================
Hans Beierle wrote
>We have applications building up directories with 50000+ files and
>encountered due to this size also various timeout problems during backup
>runs. Same as others did, we fixed that by increasing COMMTimeout. Yet,
>I'm concerned about having to change a general option which applies
>to all client/server sessions to address a problem which relates only
>to some few clients. The install manual states about COMMTimeout:
>"The server terminates the session to release communication resources as
>soon as possible, and to ensure that database locks are not held for
>undue periods of time."
>So, I assume that COMMTimeout should be as low as possible. To get around
>these long running directory scans, the ADSM client should have a kind of
>'heartbeat' function, which tells the server that it's still alive.
We also had this problem with large directories on an OS/2 Client
where the COMMTimeout parameter had to be adjusted and felt that it
could be a problem because it is a general option.
Later we found out that there was an option called "SLOWINCREMENTAL"
which i docemented in the "Performance Tuning Guide Version 2 Release 1"
manual. The "SLOWINCREMENTAL" option in our case removed the long waits
that were triggering the COMMTimeout option.
I dont't know if the "SLOWINCREMENTAL" option is working the same way
on AIX and other platforms but it sure did help us.
/---------------------------------------------/
/ Jorgen Bentsen, SDC af 1993 A/S, Denmark /
/ dksdcamc AT ibmmail DOT com /
/---------------------------------------------/
|
|
|