The fix went into trunk as r1816619 and in 2.4.x as r1816969 in 2.4.x.
Cheers,
Stefan
> Am 02.12.2017 um 09:23 schrieb Luca Toscano :
>
> Hi everybody,
>
> did I miss an update or are we still waiting for more data? (Don't mean to
> rush you Stefan, just to understand
Hello,
here is the relevant commit:
https://github.com/icing/mod_h2/commit/51085e0c26da1f47ea9cf91930af8cef0dececb9
Stefan
Excuse my typo sent from my mobile phone.
> Am 02.12.2017 um 14:39 schrieb Stefan Priebe - Profihost AG
> :
>
> Hello Luca,
>
> It’s a problem
Hello Luca,
It’s a problem with the limited fifo queue size of http2.
Stefan send me a workaround not sure if this one will go into http2 or if he
will release a real fix soon.
Greets,
Stefan
Excuse my typo sent from my mobile phone.
> Am 02.12.2017 um 09:23 schrieb Luca Toscano
Hi everybody,
did I miss an update or are we still waiting for more data? (Don't mean to
rush you Stefan, just to understand what's the status of the thread :)
Luca
2017-11-24 15:26 GMT+01:00 Stefan Priebe - Profihost AG <
s.pri...@profihost.ag>:
> Thanks i‘ll post a log tonight with a 120s
Thanks i‘ll post a log tonight with a 120s stalled request.
Greets,
Stefan
Excuse my typo sent from my mobile phone.
> Am 23.11.2017 um 17:09 schrieb Stefan Eissing :
>
> Hey,
>
> could you try the patch below and produce such a lovely log file again?
>
Hey,
could you try the patch below and produce such a lovely log file again?
H2MaxWorkers please back to before, unconfigured. Thanks! This is a small
change that a) logs the interaction with h2_workers a bit more and makes sure
that time gets lost where I think it does. It also switches the
Hi,
Am 23.11.2017 um 14:10 schrieb Stefan Eissing:
> Interesting. I assume that otherwise this host is the same (OS/CPU etc.) as
> others where it runs without probs?
Yes and no i got some more reports by colleagues where they've disabled
http2 as the customers had unexpected long loading times.
Interesting. I assume that otherwise this host is the same (OS/CPU etc.) as
others where it runs without probs? We are not ghosted by some strange
blabla-lake hyper threading thingie singularity?
Need to think about this.
> Am 23.11.2017 um 13:43 schrieb Stefan Priebe - Profihost AG
>
*argh*, i was too fast no it did NOT fix the problem. It even happens with:
H2MaxWorkers4096
Sorry about that.
Stefan
Am 23.11.2017 um 13:42 schrieb Stefan Priebe - Profihost AG:
> Hello,,
>
> setting:
> H2MaxWorkers1024
>
> fixes the issue for me. The main problem is how to i know
Hello,,
setting:
H2MaxWorkers1024
fixes the issue for me. The main problem is how to i know how many
workers are needed? How can i detect whether all workers of h2 are busy?
Stefan
Am 22.11.2017 um 13:23 schrieb Stefan Priebe - Profihost AG:
> Hell Stefan,
>
> will send a log to you in a
Hell Stefan,
will send a log to you in a few seconds via private email.
Greets,
Stefan
Am 21.11.2017 um 23:18 schrieb Stefan Eissing:
> sorry for the late reply. for stucks trace2 is best.
>
>> Am 21.11.2017 um 19:35 schrieb Stefan Priebe - Profihost AG
>> :
>>
>>
sorry for the late reply. for stucks trace2 is best.
> Am 21.11.2017 um 19:35 schrieb Stefan Priebe - Profihost AG
> :
>
> Hello Stefan,
>
> which loglevel do you need? trace2?
>
> Greets,
> Stefan
>
>> Am 21.11.2017 um 16:48 schrieb Stefan Eissing:
>> Never done
Hello Stefan,
which loglevel do you need? trace2?
Greets,
Stefan
Am 21.11.2017 um 16:48 schrieb Stefan Eissing:
> Never done this, but https://www.howtoforge.com/setenvif_apache2 seems like
> one way to do make it work.
>
>> Am 21.11.2017 um 16:16 schrieb Stefan Priebe - Profihost AG
>>
On Tue, Nov 21, 2017 at 10:48 AM, Stefan Eissing
wrote:
> Never done this, but https://www.howtoforge.com/setenvif_apache2 seems like
> one way to do make it work.
That is unfortunately for access logs. For error logs you'd need
something like and LogLevel but
Never done this, but https://www.howtoforge.com/setenvif_apache2 seems like one
way to do make it work.
> Am 21.11.2017 um 16:16 schrieb Stefan Priebe - Profihost AG
> :
>
>
> Am 21.11.2017 um 16:06 schrieb Stefan Priebe - Profihost AG:
>> Am 21.11.2017 um 15:45 schrieb
Am 21.11.2017 um 16:06 schrieb Stefan Priebe - Profihost AG:
> Am 21.11.2017 um 15:45 schrieb Stefan Eissing:
>>
>>> Am 21.11.2017 um 14:33 schrieb Stefan Priebe - Profihost AG
>>> :
>>>
>>> Hello Stefan,
>>> Hello Yann,
>>>
>>> me the http2 bug tester is calling again
Am 21.11.2017 um 15:45 schrieb Stefan Eissing:
>
>> Am 21.11.2017 um 14:33 schrieb Stefan Priebe - Profihost AG
>> :
>>
>> Hello Stefan,
>> Hello Yann,
>>
>> me the http2 bug tester is calling again ;-)
>
> And the day was going so well...
I'm sorry ;-)
>> While
> Am 21.11.2017 um 14:33 schrieb Stefan Priebe - Profihost AG
> :
>
> Hello Stefan,
> Hello Yann,
>
> me the http2 bug tester is calling again ;-)
And the day was going so well...
> We've the problem "most probably" since apadhe 2.4.29 that http2 stucks
> from time to
Hello Stefan,
Hello Yann,
me the http2 bug tester is calling again ;-)
We've the problem "most probably" since apadhe 2.4.29 that http2 stucks
from time to time.
While running two bash curl while loops the one using http1.1 always
finishes in < 0.05s while the http2 one takes sometimes 0.4 to
19 matches
Mail list logo