thanks for the info, sounds like the NTLM auth is not considering the
fact that keep alives are optional, and can be controlled by the server.
so it's really a problem with the client, not the server in this case.
but its good to know you found a workaround
Filip
Sanglard Fabien wrote:
Hello,
It seems Tomcat 6 will close a connection even tough the browser requested it to remain
open via a "Connection: Keep-Alive"
header if the ration (usedThread/totalThread) > 0.75 (Is this meant to prevent outage or DOS ?)
Http11Processor.java (line 778)
if (threadRatio > 75)=20
{
keepAliveLeft =3D 1;
}
If this is documented, I was unable to find it .
This feature was the source of an issue when my intranet
application started to get popular and reached 10 millions hits a day.
NTLM authentication handshake (which require 2 HTTP GET) was being terminated with a "Connection: Close" header right away and no-one could access the application during very busy hours.
The solution was to raise maxThread in the connector to
100 (default is 40), hence reducing the ratio.
It now works like a charm.
Maybe it will help someone.
Fabien Sanglard
__________________________________________________
Do You Yahoo!?
En finir avec le spam? Yahoo! Mail vous offre la meilleure protection possible contre les messages non sollicités
http://mail.yahoo.fr Yahoo! Mail
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
