httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tapan Nanawati" <Tapan.Nanaw...@integral.com>
Subject RE: Client TCP Connections go to FIN state after each request
Date Mon, 12 Nov 2007 20:06:14 GMT
Hi Ruediger 
Thanks very much.
This bug fix solves my problem!
Cheers
Tapan
 

-----Original Message-----
From: Ruediger Pluem [mailto:rpluem@apache.org] 
Sent: Friday, November 09, 2007 2:55 PM
To: dev@httpd.apache.org
Subject: Re: Client TCP Connections go to FIN state after each request



On 11/09/2007 08:40 PM, Tapan Nanawati wrote:
> Hi
> I am trying to upgrade from apache 2.2.4 to 2.2.6 on Red Hat AS4
> update4-x64  configuration
> 
> I compiled apache with following options. My 2.2.4 apache was also 
> compiled with below configuration.
> 
> ./configure --enable-proxy --enable-proxy-http --enable-proxy-connect 
> --enable-proxy-ftp --enable-http-core --enable-rewrite --enable-ssl 
> --enable-deflate --enable-expires --enable-so --enable-headers 
> --enable-logio --with-ssl=/cust/openssl-0.9.8f
> --prefix=/usr/opt/apache2 --with-mpm=prefork --enable-maintainer-mode
> 
> 
> I connected 2.2.6 using the httpd.conf file which I was using in 2.2.4.
> 
> I collected tcpdump { tcpdump -s 0 host webServ -w dump.log } on one 
> of the servers where apache was proxypassing requests.
> On analysing with etheral I observe that apache is closing the 
> connection after every request.
> Here is a section from etheral which keeps repeating after every
> request->
> 
> Header
> "No","time","Source","destination","protocol","Info logicalport > 
> listening port [Status]...... "
> 
> Data ->
> "3","0.018626","208.246.226.171","208.246.226.166","TCP","33164 > 9380 
> [FIN, ACK] Seq=0 Ack=1379 Win=17 Len=0 TSV=380276575 TSER=327971424"
> 
> Then next request starts from next port ->
> "4","0.018668","208.246.226.171","208.246.226.166","TCP","33165 > 9380 
> [SYN] Seq=0 Len=0 MSS=1460 TSV=380276575 TSER=0 WS=9"
> 
> 
> This problem is not there when I connect with 2.2.4 to the same server.

I cannot reproduce this problem. Please open up a bug in bugzilla and attach

1. Your configuration.
2. Your tcpdumps with -s 1500.

But maybe I just understood you wrong and you are affected by PR 43472 (https://issues.apache.org/bugzilla/show_bug.cgi?id=43472).

Regards

RĂ¼diger


Mime
View raw message