On 19.11.2011 06:07, Jeremy wrote:
OK, we figured it out. It's a case of too many timeout settings and not
having a real DevOps person on hand. There was an obvious error message in
Apache's mod_jk.log that I failed to correlate with the problem because I
misread the timestamp on one of the
OK, we figured it out. It's a case of too many timeout settings and not
having a real DevOps person on hand. There was an obvious error message in
Apache's mod_jk.log that I failed to correlate with the problem because I
misread the timestamp on one of the many log entries. Doh!
[info]
Mark, thanks for taking a crack at this. I'm not that familiar with how
mod_jk and AJP work under the covers, but based on my level of
understanding, your scenario comes close but does not exactly match the
logging we see. My detailed comments below.
On Wed, Nov 16, 2011 at 11:53 PM, Mark
On 17/11/2011 08:48, Jeremy wrote:
Mark, thanks for taking a crack at this. I'm not that familiar with how
mod_jk and AJP work under the covers, but based on my level of
understanding, your scenario comes close but does not exactly match the
logging we see. My detailed comments below.
On
OK, I know this seems crazy, but I've looked long and hard and cannot
explain this as other than a Tomcat bug. I'm more than willing to dig up
extra information where I can, but this is a very rare problem seen in
production and not reproducible at will. Also, because this is in
production,
Bypass the apache and send the POST request to tomcat directly. Thant will
tell you where the problem is tomcat or apache.
On Thu, Nov 17, 2011 at 12:29 PM, Jeremy asfbugzi...@nuru.net wrote:
OK, I know this seems crazy, but I've looked long and hard and cannot
explain this as other than a
From: Jeremy [mailto:asfbugzi...@nuru.net]
Subject: Single POST request being handled twice
How is it possible that Tomcat has 2 threads handling
the same request?
This is usually the result of an application coding or design error: storing a
reference to a request in an inappropriate
...@nuru.net]
Subject: Single POST request being handled twice
How is it possible that Tomcat has 2 threads handling
the same request?
This is usually the result of an application coding or design error:
storing a reference to a request in an inappropriate scope such as the
session
On 17/11/2011 01:29, Jeremy wrote:
OK, I know this seems crazy, but I've looked long and hard and cannot
explain this as other than a Tomcat bug. I'm more than willing to dig up
extra information where I can, but this is a very rare problem seen in
production and not reproducible at will.
