I am waiting to hear back from the peeps that opened the github issue. From how 
I read their logs, the patch should help them. Will report what they say. 

-Stefan

> Am 25.07.2017 um 15:40 schrieb Stefan Eissing <stefan.eiss...@greenbytes.de>:
> 
> Well, if the customer could reproduce this at a 
> 
>  LogLevel http2:trace2
> 
> that would help.
> 
>> Am 25.07.2017 um 15:38 schrieb Stefan Priebe - Profihost AG 
>> <s.pri...@profihost.ag>:
>> 
>> Hello Stefan,
>> 
>> thanks for the patch. No it does not solve the problem our customer is
>> seeing.
>> 
>> What kind of details / logs you need?
>> 
>> Greets,
>> Stefan
>> 
>>> Am 25.07.2017 um 11:59 schrieb Stefan Eissing:
>>> The issue was opened here: https://github.com/icing/mod_h2/issues/143
>>> 
>>> I made a patch that i hope addresses the problem. The 2.4.x version I 
>>> attach to this mail.
>>> 
>>> Thanks!
>>> 
>>> Stefan
>>> 
>>> 
>>> 
>>> 
>>> 
>>>> Am 25.07.2017 um 08:13 schrieb Stefan Priebe - Profihost AG 
>>>> <s.pri...@profihost.ag>:
>>>> 
>>>> 
>>>>> Am 24.07.2017 um 23:06 schrieb Stefan Eissing:
>>>>> I have another report of request getting stuck, resulting in the error 
>>>>> you noticed. Will look tomorrow and report back here what I find.
>>>> 
>>>> Thanks, if you need any logs. Pleae ask.
>>>> 
>>>> Stefan
>>>> 
>>>>> 
>>>>>> Am 24.07.2017 um 22:20 schrieb Stefan Priebe - Profihost AG 
>>>>>> <s.pri...@profihost.ag>:
>>>>>> 
>>>>>> Hello all,
>>>>>> 
>>>>>> currently 8 hours of testing without any issues.
>>>>>> 
>>>>>> @Stefan
>>>>>> i've most probably another issue with http2 where some elements of the
>>>>>> page are sometimes missing and the connection results in
>>>>>> ERR_CONNECTION_CLOSED after 60s. What kind of details do you need?
>>>>>> 
>>>>>> Greets,
>>>>>> Stefan
>>>>>>>> Am 22.07.2017 um 13:35 schrieb Yann Ylavic:
>>>>>>>> On Sat, Jul 22, 2017 at 2:18 AM, Yann Ylavic <ylavic....@gmail.com> 
>>>>>>>> wrote:
>>>>>>>> On Fri, Jul 21, 2017 at 10:31 PM, Stefan Priebe - Profihost AG
>>>>>>>> <s.pri...@profihost.ag> wrote:
>>>>>>>>> 
>>>>>>>>> your new defer linger V3 deadlocked as well.
>>>>>>>>> 
>>>>>>>>> GDB traces:
>>>>>>>>> https://www.apaste.info/LMfJ
>>>>>>>> 
>>>>>>>> This shows the listener thread waiting for a worker while there are
>>>>>>>> many available.
>>>>>>>> My mistake, the worker threads failed to rearm their idle state for
>>>>>>>> the deferred close case.
>>>>>>>> 
>>>>>>>> V4 available, thanks Stefan!
>>>>>>> 
>>>>>>> Since I didn't want you to test again something that fails quickly, I
>>>>>>> did some stress tests myself this time with several tools, with V5
>>>>>>> (same as V4 from a 2.4.x POV).
>>>>>>> 
>>>>>>> It seems to work well here...
>>>>>>> 
>>>>>>>> Regards,
>>>>>>>> Yann.
>>>>> 
>>> 
> 

Reply via email to