https://bz.apache.org/bugzilla/show_bug.cgi?id=63010
Yann Ylavic changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bz.apache.org/bugzilla/show_bug.cgi?id=63010
--- Comment #11 from Cristian Duca ---
Hello, Yann,
I have compiled successfully apache on windows.
I have implemented the changes from Comment7 for the mod_proxy_hcheck module.
I can confirm that the fix from Comment7 works without any worka
https://bz.apache.org/bugzilla/show_bug.cgi?id=63010
--- Comment #10 from Cristian Duca ---
Hello, Yann,
I have tested the workaround by adding more ProxyHCTPSize.
Now I am trying to compile Apahce on Windows and to test the coding changes
from comment 7 without any mitigations added into the A
https://bz.apache.org/bugzilla/show_bug.cgi?id=63010
--- Comment #9 from Yann Ylavic ---
Hi Cristian,
(In reply to Cristian Duca from comment #8)
>
> I work with Tudor.
> We already implemented that fix and it works as expected -> apache is stable
> and we are not encountering any memory leaks
https://bz.apache.org/bugzilla/show_bug.cgi?id=63010
--- Comment #8 from Cristian Duca ---
Hello Yann,
I work with Tudor.
We already implemented that fix and it works as expected -> apache is stable
and we are not encountering any memory leaks issues.
We have configured our hcinterval at 10 seco
https://bz.apache.org/bugzilla/show_bug.cgi?id=63010
--- Comment #7 from Yann Ylavic ---
Created attachment 37621
--> https://bz.apache.org/bugzilla/attachment.cgi?id=37621&action=edit
Avoid concurrent checks
This patch resets the timestamp during the check (and prevents re-entering the
check
https://bz.apache.org/bugzilla/show_bug.cgi?id=63010
--- Comment #6 from Tudor Tudorache ---
We are running into the same issue with our current configuration. Apache
develops a serious memory leak hitting over 1.2 GB if one of the JVM's are
started or stopped. We were on Apache 2.4.26 previously
https://bz.apache.org/bugzilla/show_bug.cgi?id=63010
--- Comment #5 from Jim Jagielski ---
Thanks for the incredible bug report and the excellent investigation. I agree
that Fixes 1+2 make the most sense. I'll look into adding them asap.
--
You are receiving this mail because:
You are the assig
https://bz.apache.org/bugzilla/show_bug.cgi?id=63010
--- Comment #4 from WJCarpenter ---
I've spent quite a bit of time over the last few days trying to understand what
goes on here. I have reproduced the memory growth on both Windows and Linux
with Apache httpd 2.4.46. It doesn't depend on healt
https://bz.apache.org/bugzilla/show_bug.cgi?id=63010
Christophe JAILLET changed:
What|Removed |Added
Blocks||61499
Referenced Bugs:
https://
https://bz.apache.org/bugzilla/show_bug.cgi?id=63010
--- Comment #3 from pawel.c ---
Replicable also on 39, Windows Server 2012
It is about health check memory leaks depends on frequency.
To reproduce...
(1) You have to have more than one high freq health check like...
ProxyHCExpr wsOK {%{REQU
https://bz.apache.org/bugzilla/show_bug.cgi?id=63010
--- Comment #2 from CFindley ---
Note: we have a very lengthy and aged httpd.conf file which has cruft from
years of fixing defects and adding new options, so it is entirely possible this
is some artifact of that. I did try setting up a very si
https://bz.apache.org/bugzilla/show_bug.cgi?id=63010
WJCarpenter changed:
What|Removed |Added
OS||All
CC|
https://bz.apache.org/bugzilla/show_bug.cgi?id=63010
--- Comment #1 from CFindley ---
Created attachment 36324
--> https://bz.apache.org/bugzilla/attachment.cgi?id=36324&action=edit
error.log output covering 2-tenths of a second/5k lines
--
You are receiving this mail because:
You are the ass
14 matches
Mail list logo