Re: [jetty-dev] 8.1.2.v20120308 - rare mixup of requests

[Jesse McConnell <jesse.mcconnell@xxxxxxxxx>]

"I expect some kind situation where (jetty) threads/processes overlap
in very unfortunate ways."

it is easy to start waving hands at this sort of general 'multi thread
ah!' area but this issue really needs to get some specifics going or
it isn't going to go anywhere

if we can't reproduce it, we probably can't fix it with any certainty,
nor can we pour massive amounts of time into something that appears to
be completely isolated to a edge case that one use case is seeing.  It
would be far easier to see this happening do to an issue in whatever
is running on top of jetty for this use case then it being with jetty
itself.  In otherwords, if it can't be reproduced in a small app on
jetty that is dealing with huge requests/responses like your speaking
about here and it only happens with X other systems are in play on top
of jetty...then it is hard to start from the position that jetty is to
blame.

Now..I am not saying this is not an issue in jetty...but before this
issue goes any further I think we would really like to see it happen
on the latest jetty release of 8.1.7 since we know there were a number
of little tweaking to the networking code in there and perhaps there
was a race condition like you mention in the early 8.1.x releases that
has already been addressed.

cheers,
jesse

--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx


On Fri, Oct 26, 2012 at 1:16 PM, Per Steffensen <steff@xxxxxxxxxxxxx> wrote:
> Thomas Becker skrev:
>
>> Per, I've had a look at all the information you've send me. I've been
>> interested in the request body and not the response for sure, but you've
>> sent that information anyhow.
>>
>> Your request body is pretty big and you might hit some limit here. I've
>> had a rough look at our code and I think if that would be really the case
>> you should see some exception.
>
> I see no exception - at least not around this particular request when the
> bug occurs.
>
>> On monday I will write a small test case trying to send and parse your
>> request bodies and see what happens on jetty.
>
> Hmmm, good luck, but I dont think you will have any luck reproducing the
> bug. I have to mention that we have tried to modify our big data-integrity
> test so that it just resend the exact same request again if (it seems like)
> the request failed due to this bug. And we are successful during this second
> attempt at the exact same request (unless we hit the same bug again, but
> that is very very very rare). So I belive I can say that it is not the
> content of the request or anything. I must be something that happens under
> very unfortunate circumstances - I expect some kind situation where (jetty)
> threads/processes overlap in very unfortunate ways.
>
>> Maybe I'll also do some concurrent tests with big load sending large
>> request bodies.
>
> You might be more lucky there, but dont get your hopes up. It is a very very
> rare bug, I believe. We have several concurrent unit-test-sized tests at our
> side that never revealed this problem.
>
>>
>> However I need you to file a bugzilla and add all the information you have
>> as you're the bug reporter. Please add everything you discovered and
>> described in your emails to that bugzilla:
>>
>> https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Jetty&format=guided
>
> Ok. I did my best at: https://bugs.eclipse.org/bugs/show_bug.cgi?id=392936
>
>>
>> Thanks and have a good weekend.
>
> You too!
>
>>
>> On 10/26/12 4:13 PM, Per Steffensen wrote:
>>>
>>> Ups, forgot to say that I can make a BugZilla, but that I would prefer if
>>> you would do it, just to be sure that it is expressed and formatted as you
>>> want it.
>>>
>>> Regards, Per Steffensen
>>
>>
>>
>
> _______________________________________________
> jetty-dev mailing list
> jetty-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jetty-dev