Re: [jetty-users] Bug between 9.2.3 and 9.2.5

[Ben Summers <ben@xxxxxxxxxxxx>]

Jan Bartel <janb@xxxxxxxxxxx> wrote:
> 
> Hi Ben,
> 
> Sounds like a bug that has been fixed for 9.2.6 (which is just about
> to come out). Here's at least one reference to a bugzilla report that
> seems like it is the bug you're experiencing:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=454452
> 
> And here's the bug that was the root cause:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=452246


Those two bug reports sound awfully familiar!

It sounds like I shouldn't spend any more time on this, then put 9.2.6 on staging and watch it carefully.

Thank you for saving me a load of time, and of course for Jetty itself.

Ben




> On 10 December 2014 at 14:37, Ben Summers <ben@xxxxxxxxxxxx> wrote:
>> 
>> Hello,
>> 
>> I'm chasing a bit of a strange bug. I'm wondering if anyone can suggest how I should go about generating a reproducible test case.
>> 
>> I've got one particular response which is almost entirely sent, then there's a delay of approx 30 seconds, then the final bit arrives and the page rendering is completed. It happens the same in Firefox, Chrome and Safari.
>> 
>> It's from an embedded Jetty 9.2.5 returning a web page which is 438368 bytes uncompressed, 71418 bytes compressed, with about 262 bytes of headers, over an SSL connection.
>> 
>> The gzipping is done by our app, not jetty. It's sent by calling servletResponse.getOutputStream() then write() on the stream via a GZIPOutputStream with an 8k buffer.
>> 
>> I'm almost certain the write() returns quickly, and as far as the app is concerned, it finished handling the request in a few milliseconds.
>> 
>> It's pretty much 100% repeatable.
>> 
>> Reverting to 9.2.3 solves the problem.
>> 
>> I'm running on a Solaris derivative:
>> 
>>   java version "1.7.0_71"
>>   Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
>>   Java HotSpot(TM) Server VM (build 24.71-b01, mixed mode)
>> 
>> I can't seem to reproduce this outside our production environment with data I can't share. I've tried generating all sorts of responses of about this size, and even using the text of the offending response, all to no avail.
>> 
>> Any suggestions welcomed!
>> 
>> Thanks,
>> 
>> Ben
>> 
>> 
>> 
>> 
>> _______________________________________________
>> jetty-users mailing list
>> jetty-users@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/jetty-users
> 
> 
> 
> -- 
> Jan Bartel <janb@xxxxxxxxxxx>
> www.webtide.com
> 'Expert Jetty/CometD developer,production,operations advice'
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Wed, 10 Dec 2014 07:46:25 -0800
> From: Antonio Ye <antonioye@xxxxxxxxx>
> To: jetty-users@xxxxxxxxxxx
> Subject: [jetty-users]
> 	AsyncProxyServlet.StreamReader.onRequestContent()
> Message-ID:
> 	<CAJmbGnq4ZiRXdSiCZ_51Lu+rdAgba4kpUQvyuUfxMLGC0B7Chg@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset=UTF-8
> 
> Anyone know if the header information is guaranteed to be be available
> in the request object when
> AsyncProxyServlet.StreamReader.onRequestContent() gets called?
> 
> 
> ------------------------------
> 
> _______________________________________________
> jetty-users mailing list
> jetty-users@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/jetty-users
> 
> End of jetty-users Digest, Vol 67, Issue 8
> ******************************************

--
http://bens.me.uk