tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <>
Subject Re: Http 500 and %b in access log
Date Wed, 20 Jan 2010 18:47:40 GMT
Hash: SHA1


On 1/20/2010 12:06 PM, Mohit Anchlia wrote:
> Tomcat 6:

Which specific version, please. Also, what connector(s) are you using.
Please provide the configuration for them. Are you using another web
server in front of Tomcat? If so, which one, and how are you connecting
them (mod_jk, mod_proxy_ajp, mod_proxy_http, etc.)?

> I am seeing Exception in localhost
> Read time out. I looked at the access log and I see tomcat returning
> Http 500. Only thing in common is that "%b" (bytes sent) for all the
> timeouts are 2657. For rest of them where requests are successful
> it's less than 2657.

Interesting. Do all responses with fewer than 2657 bytes succeed? Do all
responses with more than 2656 bytes fail?

Please post the entire stack trace of the exception.

> Could someone help me understand what %b is for in localhost access
> logs and if what I am seeing makes sense.

%b is, as you say, the number of bytes sent (presumably to the client,
in the response).

Does this always fail with certain clients? If so, which ones? Are these
normal web browsers, or are you using a custom client?

> Does SocketTimeoutException correspond to ConnectionTimeout in the
> connector? We tried increasing it but didn't make any difference.

ConnectionTimeout is how long the connector will wait after a connection
is established for the request to come from the client.

There really isn't a setting on the standard HTTP connector that will
cause a timeout to occur when writing to the connection.

- -chris
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla -


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message