Filip Hanik - Dev Lists wrote:
As far as I know, the accumulated request processing times retrieved
via the MBeans for Servlets or the GlobalRequestProcessor are correct.
I simply don't want to break them.
I had a quick look, and our confusion might come from the fact, that
RequestInfo contai
Rainer Jung wrote:
Filip Hanik - Dev Lists wrote:
Rainer Jung wrote:
Hi Filip,
I guess that also fixes the misleading html manager display (request
times going up and up). That would be very nice.
Just a quick shot:
- maybe you can fix Procssing -> Processing everywhere
not sure what you
Filip Hanik - Dev Lists wrote:
Rainer Jung wrote:
Hi Filip,
I guess that also fixes the misleading html manager display (request
times going up and up). That would be very nice.
Just a quick shot:
- maybe you can fix Procssing -> Processing everywhere
not sure what you mean?
Simply a typ
no strong opinion either way.
-Original Message-
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] Sent:
Monday, September 24, 2007 11:49 AM
To: Tomcat Developers List
Subject: 6.0.x request processing patch
Currently, the RequestInfo.getRequestProcessingTime is not taking
i
trong opinion either way.
-Original Message-
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] Sent:
Monday, September 24, 2007 11:49 AM
To: Tomcat Developers List
Subject: 6.0.x request processing patch
Currently, the RequestInfo.getRequestProcessingTime is not taking
into a
, September 24, 2007 11:49 AM
To: Tomcat Developers List
Subject: 6.0.x request processing patch
Currently, the RequestInfo.getRequestProcessingTime is not
taking into
account if the request is active or not, hence returning a larger and
larger value if a new request is not received.
The patch
, September 24, 2007 11:49 AM
To: Tomcat Developers List
Subject: 6.0.x request processing patch
Currently, the RequestInfo.getRequestProcessingTime is not
taking into
account if the request is active or not, hence returning a larger and
larger value if a new request is not received.
The patch
t Developers List
> Subject: 6.0.x request processing patch
>
> Currently, the RequestInfo.getRequestProcessingTime is not
> taking into
> account if the request is active or not, hence returning a larger and
> larger value if a new request is not received.
> The pat
Currently, the RequestInfo.getRequestProcessingTime is not taking into
account if the request is active or not, hence returning a larger and
larger value if a new request is not received.
The patch addresses the following
1. getRequestProcessingTime returns 0 if no request is active
2. getLastR
