Thanks for the response. That's what I think. But why does the out of order entry happens in 4-5 mins late everytime? If the out of order is because of multi-threading, it shouldn't appear so late and cause the EOFException in the Tomcat end. Michael -----Original Message----- From: Joshua Slive [mailto:jslive@xxxxxxxxx] Sent: Monday, May 02, 2005 11:40 AM To: users@xxxxxxxxxxxxxxxx Subject: Re: [users@httpd] question about timestamp in access.log On 5/2/05, Michael Lu <MLu@xxxxxxxxxxxxx> wrote: > I have a question about what timestamp means in access.log files. It says > it's the time when apache server finish process the request from the client > in the online document. In fact, the docs are wrong. This was changed a while ago to use the time the request was received. This violates the common log format requirements, but makes logging faster. So it is not unexpected to see out-of-order log lines. Joshua. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|