-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 All,
I suspect I already know the answer to this, but I wanted to double-check. Requests are logged to the access log in the order in which they were accepted from the connector, right? Or, if they can't be guaranteed to be de-queued-and-dispatched serially (because there are multiple acceptor threads), they are at least logged (or queued to be logged) as soon as possible? I'm asking because we are observing an external process that should be making two separate, serial requests us (that is, request A is made and completes before request B is made) and in some cases request B is appearing in the access log before request A is showing up. There is a ton of other circumstantial evidence that this external process is in fact /not/ waiting for request A to be processed before making request B, but I just wanted to double-check. Of course the first response when asking if maybe someone else's code isn't working properly is to have them ask *you* if you're sure *your* code is working properly ;) So, this is my due diligence to determine if, in addition to the mountain of evidence we otherwise have, Tomcat does in fact log requests in the order in which they are received. We are using the following format string: "%a %t "%r" %s %D" The value of "%t" is the interesting one, of course, but it's resolution is only in seconds, and we are seeing an access log file like this: 127.0.0.1 [18/Apr/2013:16:19:08 -0400] "POST /request/B HTTP/1.1" 200 108 127.0.0.1 [18/Apr/2013:16:19:08 -0400] "POST /request/A HTTP/1.1" 200 263 Thanks, - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJRcGyJAAoJEBzwKT+lPKRYBOQP/3Hq+9vqqDazy+2mzKADtaUZ ycTjjs4BCQWQoW7OJxweGkMp2hr84QcZmdx/K2f3AzYPBmuVBpym8BpIOj0Cj4aM sTJFcnN5Tu8zXj38FZkOKhBDEXrnCL1/Vvk4+NFc7K43UpgsKq82MMtLHe0fI512 GPF6GiBapyRg/EA3Zi5xqn0PZzghmWW1ZPAUkImffXt3c2OXndYaqPjMJuueg3n4 NNtBINbXoy5caQ/CFzZK+QBAIV4Uo9uBlo6sc3bpLAmwYpjfcXuVZuhSuMnpjQk8 /VGdGKMHmL8Xjiv2p6RRw6XcpUPoodo94ZAtPep4rrS5RiOPMUtLRClpFLvgxfGU hbgbHe+EUIVIxlXkvn45T9aeGfg1qbjqszkH6RSgG6ct9WoGzymA3PJ6petHKRE7 cz5UsNg9mFRdDQ++aCUwPbUwGaqS4+ga+PJGZUb+N1L8fTdlXBDoMpdbMfKdfeTK rqSQL4M6EK4ruNXvkMaYPasYVTwQ468DV0CT62SFfVCuXupmfGAgckWX3A4/rPuR aWMtK1UKDi7sNlefB3Tf0fdJd3Au9Pv2hfFidE4N7j20GP3jfo4THP0kwnjW/Zqj zZaHy4zWCzs3JMBfqBCuIfjHccqq9TyCZA9NtktZYdpHHTgYgdM9Dnr0Ae/XTX0b hIhQdAr/BDcsXwK6aUbf =7812 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
