Will do, please give me a day.
--
-bk
-Original Message-
From: Mladen Turk [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 21, 2007 11:27 AM
To: Brandon Knitter
Cc: Tomcat Users List
Subject: Re: JK ISAPI Filter and Keep-Alive/Chunked Encoding (a.k.a. Is
1.2.21 broken?)
Brandon
.
In 1.2.21 I'm seeing absolutely no Keep-Alive is performed, even when
the content-length is known and the browser is sending a Connection:
Keep-Alive request.
Thoughts?
--
Brandon Knitter - [EMAIL PROTECTED]
NVIDIA - http://www.nvidia.com/
v: 408/566-6699
c: 408/717-1274
-Original Message-
From: Mladen Turk [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 20, 2007 10:37 AM
To: Tomcat Users List
Subject: Re: JK ISAPI Filter and Keep-Alive/Chunked Encoding (a.k.a. Is
1.2.21 broken?)
Brandon Knitter wrote:
In 1.2.21 I'm seeing absolutely no Keep-Alive is performed
Ugh! But that made it work! :)
--
-bk
-Original Message-
From: Martin Skøtt [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 25, 2007 12:58 PM
To: Tomcat Users List
Subject: Re: 64-bit tomcat5.exe not working properly (TC 5.5.20)
A reply for archives...
The amd64 files in the SVN
Turns out the Jetty (mortbay) configuration has a MaxTimeIdleMs setting.
This sets the SO_TIMEOUT for the connection socket. The Jetty server
was disconnecting from the client, leaving an unclean shutdown of the
socket.
I found that the connection would sit in a FIN_WAIT2 state for a long
time.
.
This is *not* related to the worker keepalive setting.
If there a workaround or configuration for this? I see this plugin
professes they support HTTP Keep-Alive, is this a farse?
http://www.jspisapi.com/
--
Brandon Knitter - [EMAIL PROTECTED]
NVIDIA - http://www.nvidia.com/
v: 408/566-6699
c: 408
We are getting the following entries in the logs frequently:
[Sun Oct 15 09:31:35 2006] [6108:0516] [error]
ajp_connection_tcp_get_message::j
k_ajp_common.c (947): (worker2) can't receive the response message from
tomcat,
network problems or tomcat is down (172.17.96.97:9080), err=-60
[Sun Oct 15
