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

Subject: Re: 3rd parth app communicating with HTTP instance over looback 127.0.0.1 - RST occurring which causes Error on read on socket
From: Nathan Andelin <nandelin@xxxxxxxxx>
Date: Thu, 25 Jan 2018 08:35:39 -0700
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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?

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

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

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.