Re: AccessLogVale %D with APR Connector Giving Unexpected Results

2013-02-15 Thread stevevls
just implement the timing in a Filter. I'm glad to understand why the number has changed, though, and it makes complete sense to have it be the same as Apache's interpretation. Cheers, Steve -- View this message in context: http://tomcat.10.n6.nabble.com/AccessLogVale-D-with-APR-Connector-Giving

Re: AccessLogVale %D with APR Connector Giving Unexpected Results

2013-02-14 Thread Mark Thomas
On 14/02/2013 02:22, Steve van Loben Sels wrote: Greetings. I recently upgraded from Tomcat 6.0.36 to 7.0.35 with the native APR connector, and I ran into a problem with numbers in my access Log. I use the %D (Time taken to process the request, in millis) to measure the service delivery

Re: AccessLogVale %D with APR Connector Giving Unexpected Results

2013-02-14 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 2/14/13 5:22 AM, Mark Thomas wrote: On 14/02/2013 02:22, Steve van Loben Sels wrote: Greetings. I recently upgraded from Tomcat 6.0.36 to 7.0.35 with the native APR connector, and I ran into a problem with numbers in my access Log.