× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. February 2018

RE: 3rd parth app communicating with HTTP instance overlooback127.0.0.1 - RST occurring which causes Error on read on socket

I've been working with IBM support on this.
The goal is to keep the port open (Persistent connection) on the HTTP Apache instance.
They have had me try all of the directives below, the issue actually became worse.
Went from average of 50 RST per day to over 100 RST per day.

KeepAliveTimeout 86400
TimeOut 86400
PersistentCGITimeout 86400
MaxPersistentCGITimeout 86400
CGIRecyclePersist on

IBM reached out to their HTTP development team (in China).
Below is the latest plan.

KeepAliveTimeout 86400
MaxKeepAliveRequests 0

I'm hoping this resolves the issue.

Paul

-----Original Message-----
From: Steinmetz, Paul
Sent: Thursday, January 25, 2018 12:05 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: 3rd parth app communicating with HTTP instance overlooback127.0.0.1 - RST occurring which causes Error on read on socket


KeepAliveTimeout Directive
The number of seconds Apache httpd will wait for a subsequent request before closing the connection. By adding a postfix of ms the timeout can be also set in milliseconds. Once a request has been received, the timeout value specified by the Timeout directive applies.
Setting KeepAliveTimeout to a high value may cause performance problems in heavily loaded servers. The higher the timeout, the more server processes will be kept occupied waiting on connections with idle clients.
If KeepAliveTimeout is not set for a name-based virtual host, the value of the first defined virtual host best matching the local IP and port will be used.


TimeOut Directive
The TimeOut directive defines the length of time Apache httpd will wait for I/O in various circumstances:

When reading data from the client, the length of time to wait for a TCP packet to arrive if the read buffer is empty.

For initial data on a new connection, this directive doesn't take effect until after any configured AcceptFilter has passed the new connection to the server.
When writing data to the client, the length of time to wait for an acknowledgement of a packet if the send buffer is full.
In mod_cgi and mod_cgid, the length of time to wait for any individual block of output from a CGI script.
In mod_ext_filter, the length of time to wait for output from a filtering process.
In mod_proxy, the default timeout value if ProxyTimeout is not configured.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Kevin Bucknum
Sent: Thursday, January 25, 2018 11:53 AM
To: Midrange Systems Technical Discussion
Subject: RE: 3rd parth app communicating with HTTP instance overlooback127.0.0.1 - RST occurring which causes Error on read on socket

There are two timeouts in apache, and it may be hitting the otherone.
KeepAliveTimeout and just TimeOut. I don't think we changed ours, and it is set to 30000, so that is likely not the issue.




Kevin Bucknum
Senior Programmer Analyst
MEDDATA/MEDTRON
Tel: 985-893-2550

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Steinmetz, Paul
Sent: Thursday, January 25, 2018 10:47 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: 3rd parth app communicating with HTTP instance
overlooback127.0.0.1 - RST occurring which causes Error on read on
socket

Kevin,

Normal HTTP instance created by HTTP server wizard.
HTTP instance was changed NOT to timeout.
KeepAliveTimeout 86400

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Kevin Bucknum
Sent: Thursday, January 25, 2018 11:36 AM
To: Midrange Systems Technical Discussion
Subject: RE: 3rd parth app communicating with HTTP instance over
looback127.0.0.1 - RST occurring which causes Error on read on socket

What kind of HTTP instance is it connecting to? They have timeouts
also.




Kevin Bucknum
Senior Programmer Analyst
MEDDATA/MEDTRON
Tel: 985-893-2550

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On
Behalf Of
Steinmetz, Paul
Sent: Thursday, January 25, 2018 10:30 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: 3rd parth app communicating with HTTP instance over
looback127.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
--
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
--
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
--
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
--
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

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.