From our archives, I found the reason we changed TCPKEEPALV to 5 minutes.
With some of our production jobs, if there was issue, the application would send us notification until the TCPKEEPALV time exceeded.
So if set at 60, took an hour.
If 120, took 2 hours.
We wanted to know sooner that the app was in trouble, thus changing to 5 gave us the quicker notification, 5 minutes.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Christopher Bipes
Sent: Thursday, July 26, 2018 9:09 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: TCP/IP timeouts
Well it looks like our Web Sphere Server is running out of port in the pool of available out going ports, 16,000. So we have been looking at the iSeries when it appears to be the Windows WAS server.
Chris Bipes
Director of Information Services
CrossCheck, Inc.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> On Behalf Of Dan
Sent: Wednesday, July 25, 2018 3:57 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: TCP/IP timeouts
I set ours to 15 on our dev box several weeks ago in an effort to keep RDi
from losing the connection to the server. It seems to have helped.
- Dan
midrange.com
