Caldarale, Charles R wrote:
From: rapponcape [mailto:rapponc...@gmail.com]
Subject: Re: Tomcat 7.0.6 FIN_WAIT2 Connections and Connection Keep-Alive
It appears that I'll have to go back to using Apache
Note that Tomcat is also Apache.
to proxy these requests to get keep-alive behavi
> From: rapponcape [mailto:rapponc...@gmail.com]
> Subject: Re: Tomcat 7.0.6 FIN_WAIT2 Connections and Connection Keep-Alive
> It appears that I'll have to go back to using Apache
Note that Tomcat is also Apache.
> to proxy these requests to get keep-alive behavior to
>
On Fri, Sep 30, 2011 at 11:34 AM, André Warnier wrote:
> rapponcape wrote:
>>
>> On Fri, Sep 30, 2011 at 4:51 AM, André Warnier wrote:
>>>
>>> Rainer Jung wrote:
On 29.09.2011 22:49, rapponcape wrote:
>>
>> Aha, the client is using HTTP 1.0 and not 1.1. This could be one
>>
rapponcape wrote:
On Fri, Sep 30, 2011 at 4:51 AM, André Warnier wrote:
Rainer Jung wrote:
On 29.09.2011 22:49, rapponcape wrote:
Aha, the client is using HTTP 1.0 and not 1.1. This could be one reason
for Tomcat closing the connection. See below.
When I reconfigure and put Apache in front
On Fri, Sep 30, 2011 at 4:51 AM, André Warnier wrote:
> Rainer Jung wrote:
>>
>> On 29.09.2011 22:49, rapponcape wrote:
Aha, the client is using HTTP 1.0 and not 1.1. This could be one reason
for Tomcat closing the connection. See below.
>>> When I reconfigure and put Apache in
Rainer Jung wrote:
On 29.09.2011 22:49, rapponcape wrote:
Aha, the client is using HTTP 1.0 and not 1.1. This could be one reason
for Tomcat closing the connection. See below.
When I reconfigure and put Apache in front of Tomcat and use a jkmount with
AJP connector, response is normal and with
On 29.09.2011 22:49, rapponcape wrote:
>> Aha, the client is using HTTP 1.0 and not 1.1. This could be one reason
>> for Tomcat closing the connection. See below.
>>
>
> When I reconfigure and put Apache in front of Tomcat and use a jkmount with
> AJP connector, response is normal and without erro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
wr,
On 9/29/2011 4:49 PM, rapponcape wrote:
>> Aha, the client is using HTTP 1.0 and not 1.1. This could be one
>> reason for Tomcat closing the connection. See below.
>
> When I reconfigure and put Apache in front of Tomcat and use a
> jkmount with
Thanks for your reply. Followup
>
> 7.0.6 was not ment for production use. Start with the latest 7.0 release.
>
Will attempt to test with latest stable 7.0.21
>
> Aha, the client is using HTTP 1.0 and not 1.1. This could be one reason
> for Tomcat closing the connection. See below.
>
When
On 29.09.2011 18:28, rapponcape wrote:
> Tomcat version 7.0.6 listening on local machine 10.3.4.7 and accepting
> incoming POST connections from 4 remote machines, 10.12.5.10[2-5].
> Configured in standalone mode, using HTTP connector.
7.0.6 was not ment for production use. Start with the latest 7
Tomcat version 7.0.6 listening on local machine 10.3.4.7 and accepting
incoming POST connections from 4 remote machines, 10.12.5.10[2-5].
Configured in standalone mode, using HTTP connector.
Remote machines are sending constant stream of POST messages...~100 kbit/sec.
All POST traffic is accepted
11 matches
Mail list logo
