Re: [opensuse] Tcp reset to mainframe
- From: Anders Johansson <ajohansson@xxxxxxx>
- Date: Tue, 30 Sep 2008 16:59:10 +0200
On Tuesday 30 September 2008 16:52:02 Kain, Becki (B.) wrote:
We're continuing with this issue and I'm not even certain if it is an
issue. Our linux box (sles 9 or sles 10) opens a connection to the
mainframe (we have tcp offloading turned on since we turned it off and
it didn't change the issue), they talk, then the linux side sends a http
200 and immediately a FIN ACK before the mainframe can send anything.
This is causing exceptions on the mainframe side.
Is this really a problem and is there a way to tell the linux side to
back off? Thanks in advance
Well, FIN ACK isn't the same as a tcp reset, it just means that the linux box
wants to close the connection after a successful reply. What this probably
means is that your apache (or whatever you're using as a web server) isn't set
to try to reuse connections. The configuration keywords you want to look for
is probably KeepAlive and KeepAliveTimeout
http://httpd.apache.org/docs/2.0/mod/core.html#keepalive
It also looks like there could be a client side issue, if it's using HTTP/1.0
Anders
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
- References:
- [opensuse] Tcp reset to mainframe
- From: Kain, Becki (B.)
- [opensuse] Tcp reset to mainframe
- Prev by Date: Re: [opensuse] bash pipe
- Next by Date: Re: [opensuse] Audio doesn't work after update when using KDE, on DELL XPS 1330
- Previous by thread: [opensuse] Tcp reset to mainframe
- Next by thread: Re: [opensuse] Tcp reset to mainframe
- Index(es):
Relevant Pages
|
