RE: 3rd parth app communicating with HTTP instance over looback 127.0.0.1 - RST occurring which causes Error on read on socket

Nathan

TCP keep alive . . . . . . . . . TCPKEEPALV 5

This was changed from the default of 120 to 5 ions ago.
I think the logic here was that if there was a failure, we wanted to know sooner rather than later.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Nathan Andelin
Sent: Thursday, January 25, 2018 10:36 AM
To: Midrange Systems Technical Discussion
Subject: Re: 3rd parth app communicating with HTTP instance over looback 127.0.0.1 - RST occurring which causes Error on read on socket

Not 30 second. I mean't 30 minute timeout.

On Thu, Jan 25, 2018 at 8:32 AM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

I had never envisioned an application trying to maintain an
around-the-clock persistent connection with an HTTP server. One lives
and learns. With 50 resets per day, that sounds like about a 30 second
timeout value somewhere. Have you checked the TCPKEEPALV value of the
CFGTCPA command?

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD