By the way, I did some more testing and though I would have sworn that
destroy() prevented any further requests in Tomcat 6.0.x it also appears
to allow at least 1 additional request.
On 3/9/2011 1:44 PM, Jess Holle wrote:
On 3/9/2011 1:40 PM, Mark Thomas wrote:
On 09/03/2011 18:50, Mark Thomas wrote:
On 09/03/2011 15:47, Jess Holle wrote:
What's more troublesome to me is that with every approach I've tried at
least 1 request still gets through. In some cases this request works
normally. In other cases the request gets a 200 and no content or a
404. After this initial request things behave more appropriately --
with the particulars depending on what I try to stop.
Let me do some more testing in this area.
I can reproduce this. Fixing it shouldn't be too hard. However there are
a couple of different states:
a) Request not received when connector stopped
b) Request line being read when connector stopped
c) Request headers being read when connector stopped
d) Request body being read when connector stopped
and we need to decided how far a request has to get before it is
rejected when the connector is stopped.
I am leaning towards rejecting a) and allowing the rest to proceed.
Comments welcome at:
https://issues.apache.org/bugzilla/show_bug.cgi?id=50903
This won't get into 7.0.11 but it should make it into 7.0.12.
Thanks. Fixing this (and knowing which files to patch prior to
7.0.12's release) would be /very/ helpful.
(a) is fine by me. Any request that we've started to process even in
the slightest can proceed as far as I'm concerned -- it's preventing
any further requests from being processed that's critical.
--
Jess Holle
