looks good so war. Will wait some more days.
Greets,
Stefan
Am 19.04.2017 um 11:09 schrieb Stefan Eissing:
> Thanks, the backtraces really helped. Could you try the following patch?
>
> -Stefan
>
>
>
>
>> Am 19.04.2017 um 08:32 schrieb Stefan Priebe - Profihost AG
>> :
>>
>> Hi Stefan,
>>
>
Thanks, the backtraces really helped. Could you try the following patch?
-Stefan
h2_beam_locks_v1.diff
Description: Binary data
> Am 19.04.2017 um 08:32 schrieb Stefan Priebe - Profihost AG
> :
>
> Hi Stefan,
>
> this is now with v1.10.2 but it does not help.
>
> PID old gen:
>
> 2 15
Hi Stefan,
this is now with v1.10.2 but it does not help.
PID old gen:
2 15608 yes (old gen) 2 no 0 0 0 0 0
requests in G state:
2-2 15608 4/36/36 G 252.75 30695 41 22.10.870.87
A.B.C.D h2 XYZ:443
GET /themes/Fr
Here we go: https://github.com/icing/mod_h2/releases/tag/v1.10.2
> Am 18.04.2017 um 15:11 schrieb Stefan Eissing :
>
> In transit. Just some minutes away...
>
>> Am 18.04.2017 um 15:06 schrieb Stefan Priebe - Profihost AG
>> :
>>
>>
>> Am 18.04.2017 um 15:03 schrieb Stefan Eissing:
>>> Stefan
In transit. Just some minutes away...
> Am 18.04.2017 um 15:06 schrieb Stefan Priebe - Profihost AG
> :
>
>
> Am 18.04.2017 um 15:03 schrieb Stefan Eissing:
>> Stefan,
>>
>> that is a 1.10.0, right? That was the first version without nested locking
>> and I fixed 2 possible dead locks in 1.10
Am 18.04.2017 um 15:03 schrieb Stefan Eissing:
> Stefan,
>
> that is a 1.10.0, right? That was the first version without nested locking
> and I fixed 2 possible dead locks in 1.10.1.
>
> I am about to release a 1.10.2 with added conformity checks and a fix for
> client omitting EOF flags. Cou
Stefan,
that is a 1.10.0, right? That was the first version without nested locking and
I fixed 2 possible dead locks in 1.10.1.
I am about to release a 1.10.2 with added conformity checks and a fix for
client omitting EOF flags. Could you give that one a try?
-Stefan
> Am 18.04.2017 um 14:57
Hi,
i saw that all of them are still serving one h2 connection.
server-status:
0-3 32375 42/64/181 G 30.09 1020776 214 1285.1 2.40
5.81
h081217236127.dyn.cm.kabsi.at h2 :443GET
/wp-content/uploads/Bloglr21-8003asd.jpg HTTP/2.0
And they all
What Eric said.
With the changes in http2 worker scheduling, if I introduced a bug
in child exit there, I'd expect it to trigger via workers_pool_cleanup()
in h2_workers.c
-Stefan
> Am 18.04.2017 um 14:47 schrieb Eric Covener :
>
> On Tue, Apr 18, 2017 at 8:43 AM, Stefan Priebe - Profihost AG
>
On Tue, Apr 18, 2017 at 8:43 AM, Stefan Priebe - Profihost AG
wrote:
> bt of such a process shows:
> (gdb) bt
> #0 0x7f5df74f64db in pthread_join () from
> /lib/x86_64-linux-gnu/libpthread.so.0
Need to see the other threads in the process, this one is just waiting
for the others to complete.
Hi,
not sure whether this is related to mod_http2 v1.10.0 or is something else.
I've seen two servers where old httpd processes get stuck.
server-status looks like this:
SlotPID StoppingConnections Threads Async connections
total accepting busyidlewriting keep
11 matches
Mail list logo