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 >> <[email protected]>: >> >> 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 <[email protected]> wrote: >>>> On Fri, Jul 21, 2017 at 10:31 PM, Stefan Priebe - Profihost AG >>>> <[email protected]> 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. >
