Hi, What a quick response on this issue :)
I will try to apply the patch (i am no expert at this) and see the results. I did find another h2-related issue, but where unable to pinpoint exactly why as it where deep in ajax application, but i will see with this patch if its the same issue. Med venlig hilsen *Peter Lindegaard Hansen* *Softwareudvikler / Partner* Telefon: +45 96 500 300 | Direkte: 69 14 97 04 | Email: [email protected] Tiger Media A/S | Gl. Gugvej 17C | 9000 Aalborg | Web: www.tigermedia.dk For supportspørgsmål kontakt os da på [email protected] eller på tlf. 96 500 300 og din henvendelse vil blive besvaret af første ledige medarbejder. 2018-01-03 22:34 GMT+01:00 Lukas Tribus <[email protected]>: > Hello, > > > On Wed, Jan 3, 2018 at 9:51 PM, Willy Tarreau <[email protected]> wrote: > > On Wed, Jan 03, 2018 at 09:31:47PM +0100, Willy Tarreau wrote: > >> Oh I think you've just put your finger on it. I remember taking care > >> of handling 0-sized frames, and facing certain difficulties with them > >> (eg: sometimes returning size 0 just means nothing was done). I sounds > >> very likely that we can still have a bug around this. It would also > >> explain why your patch could get rid of it. > >> > >> I'll have a look at the code in case I have an idea. > > > > Could you please try the attached patch? I'm pretty sure it is *very* > > related to your observations. In fact till now we would not update the > > parser's state on an empty data frame, which explains why you had to > > move the stuff around. > > Yes, I can confirm this fixes the problem for me, and in a good > looking way too: all streams are correctly handled within that single > connection (no sudden connection teardown and subsequent new > connection for follow-up streams). > > Now we won't even bother the ML subscribers with a 50+ messages > mega-thread debugging an obscure H2 issue :) > > > regards, > lukas >
