[users@httpd] Calculating max workers

[Norbert Elbanbuena]

Hi,

Can I still use this formula for sizing Apache on my system?

(buffer/shared Mem - Reserved mem for other PID) / Apache PID size

I'm just wondering how to calculate max capacity for my server.

Regards,

Norbert

Re: [users@httpd] mod_proxy_hcheck response timeout?

[Yann Ylavic]

Hi Daniel,

On Thu, Apr 22, 2021 at 12:21 PM Daniel Ferradal  wrote:
>
> Is my approach correct? As with most initial approaches to a specific
> scenario, this may very well be the case, which other approach do you
> suggest?

I think that it's missing in the code but can't think of a workaround.
Does the attached patch working for you?

Regards;
Yann.
Index: modules/proxy/mod_proxy_hcheck.c
===
--- modules/proxy/mod_proxy_hcheck.c	(revision 1888249)
+++ modules/proxy/mod_proxy_hcheck.c	(working copy)
@@ -491,10 +491,12 @@ static proxy_worker *hc_get_hcworker(sctx_t *ctx,
 hc->hash.def = hc->s->hash.def = ap_proxy_hashfunc(hc->s->name, PROXY_HASHFUNC_DEFAULT);
 hc->hash.fnv = hc->s->hash.fnv = ap_proxy_hashfunc(hc->s->name, PROXY_HASHFUNC_FNV);
 hc->s->port = port;
-if (worker->s->conn_timeout_set) {
-hc->s->conn_timeout_set = worker->s->conn_timeout_set;
-hc->s->conn_timeout = worker->s->conn_timeout;
-}
+hc->s->conn_timeout_set = worker->s->conn_timeout_set;
+hc->s->conn_timeout = worker->s->conn_timeout;
+hc->s->ping_timeout_set = worker->s->ping_timeout_set;
+hc->s->ping_timeout = worker->s->ping_timeout;
+hc->s->timeout_set = worker->s->timeout_set;
+hc->s->timeout = worker->s->timeout;
 /* Do not disable worker in case of errors */
 hc->s->status |= PROXY_WORKER_IGNORE_ERRORS;
 /* Mark as the "generic" worker */

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] Apache max workers in /server-status not same as MaxWorkers in mpm_event_module

[Norbert Elbanbuena]

Thank you so much I am very clear now!

Regards,

Norbert E.


From: Eric Covener 
Sent: Monday, April 26, 2021 1:40 PM
To: users@httpd.apache.org 
Subject: Re: [users@httpd] Apache max workers in /server-status not same as 
MaxWorkers in mpm_event_module



On Mon, Apr 26, 2021 at 2:28 PM Norbert Elbanbuena 
mailto:norb...@teligentip.com>> wrote:
Hi,

$ ./apachectl -v
Server version: Apache/2.4.46 (Unix)
Server built:   Nov 15 2020 14:32:04

I just accessed /server-status?refresh=5 to regularly refresh the page.
But I think understand the counts better now. My only other question is does 
the Request column retain the last URL requested or does it clear after an x 
amount of time when the thread is idle?
I'm referring to the output below:

Srv PID Acc M   CPU SS  Req Dur ConnChild   
SlotClient  ProtocolVHost   Request
3-0 10941   0/1/1   _   0.00695 1   1   0.0 0.02
0.02192.168.237.61  http/1.1
app3.mytestapp.net:8080 GET 
/server-status?refresh=30 HTTP/1.1
3-0 10941   0/1/1   _   0.01404 0   0   0.0 0.00
0.00127.0.0.1   http/1.1
app3.mytestapp.net:8080 GET 
/manager/status?XML=true HTTP/1.1


It will stay there until the thread is reused or the process goes away. The 
"SS" column tells you how long ago that request shown completed (or started?)

Re: [users@httpd] Apache max workers in /server-status not same as MaxWorkers in mpm_event_module

[Eric Covener]

On Mon, Apr 26, 2021 at 2:28 PM Norbert Elbanbuena 
wrote:

> Hi,
>
> $ ./apachectl -v
> Server version: Apache/2.4.46 (Unix)
> Server built:   Nov 15 2020 14:32:04
>
> I just accessed /server-status?refresh=5 to regularly refresh the page.
> But I think understand the counts better now. My only other question is
> does the Request column retain the last URL requested or does it clear
> after an x amount of time when the thread is idle?
> I'm referring to the output below:
>
> Srv PID Acc M CPU SS Req Dur Conn Child Slot Client Protocol VHost Request
> *3-0* 10941 0/1/1 _ 0.00 695 1 1 0.0 0.02 0.02 192.168.237.61 http/1.1
> app3.mytestapp.net:8080 GET /server-status?refresh=30 HTTP/1.1
> *3-0* 10941 0/1/1 _ 0.01 404 0 0 0.0 0.00 0.00 127.0.0.1 http/1.1
> app3.mytestapp.net:8080 GET /manager/status?XML=true HTTP/1.1
>

It will stay there until the thread is reused or the process goes away. The
"SS" column tells you how long ago that request shown completed (or
started?)

Re: [users@httpd] Apache max workers in /server-status not same as MaxWorkers in mpm_event_module

[Norbert Elbanbuena]

Hi,

$ ./apachectl -v
Server version: Apache/2.4.46 (Unix)
Server built:   Nov 15 2020 14:32:04

I just accessed /server-status?refresh=5 to regularly refresh the page.
But I think understand the counts better now. My only other question is does 
the Request column retain the last URL requested or does it clear after an x 
amount of time when the thread is idle?
I'm referring to the output below:

Srv PID Acc M   CPU SS  Req Dur ConnChild   
SlotClient  ProtocolVHost   Request
3-0 10941   0/1/1   _   0.00695 1   1   0.0 0.02
0.02192.168.237.61  http/1.1app3.mytestapp.net:8080 GET 
/server-status?refresh=30 HTTP/1.1
3-0 10941   0/1/1   _   0.01404 0   0   0.0 0.00
0.00127.0.0.1   http/1.1app3.mytestapp.net:8080 GET 
/manager/status?XML=true HTTP/1.1

Regards,

Norbert E.


From: Rodrigo Cunha 
Sent: Monday, April 26, 2021 11:01 AM
To: users@httpd.apache.org 
Subject: Re: [users@httpd] Apache max workers in /server-status not same as 
MaxWorkers in mpm_event_module

Hi, send the inventory this host with S/O version and Apache version.
Send the command and options used for check status.

Tks.

On Mon, Apr 26, 2021 at 10:59 AM Norbert Elbanbuena 
mailto:norb...@teligentip.com>> wrote:
Hi,

I attempted to tune Apache's configuration, and used below settings:


ThreadsPerChild 64
MaxRequestWorkers 1600
MinSpareThreads 800
MaxSpareThreads 1600
ServerLimit 25
MaxConnectionsPerChild 0


But checking /server-status I only see Max workers up to 1152


Server uptime: 11 hours 20 minutes 35 seconds
Server load: 0.15 0.15 0.21
Total accesses: 57926 - Total Traffic: 279.6 MB - Total Duration: 50642985
CPU Usage: u35.7 s29.44 cu0 cs0 - .16% CPU load
1.42 requests/sec - 7.0 kB/second - 5060 B/request - 874.27 ms/request
130 requests currently being processed, 1022 idle workers
SlotPID StoppingConnections Threads Async connections
total   accepting   busyidlewriting keep-alive  closing
0   22539   no  0   yes 0   64  0   0   0
1   22540   no  0   yes 0   64  0   0   0
2   22541   no  0   yes 0   64  0   0   0
3   22743   no  0   yes 0   64  0   0   0
4   22832   no  0   yes 0   64  0   0   0
5   22833   no  3   yes 3   61  0   0   0
6   22974   no  1   yes 2   62  0   0   0
7   22975   no  3   yes 3   61  0   0   0
8   22976   no  5   yes 4   60  0   0   0
9   22983   no  4   yes 4   60  0   0   0
10  23272   no  2   yes 2   62  0   0   0
11  23273   no  6   yes 5   59  0   0   0
12  23274   no  12  yes 10  54  0   1   0
13  23280   no  12  yes 12  52  0   0   0
14  23288   no  14  yes 13  51  0   0   0
15  23300   no  20  yes 19  45  0   0   0
16  23331   no  54  yes 53  11  0   0   0
17  23370   no  0   yes 0   64  0   0   0
Sum 18  0   136 130 10220   1   0

Am I reading it incorrectly?

Regards,

Norbert Elbanbuena


--
Atenciosamente,
Rodrigo da Silva Cunha
São Gonçalo, RJ - Brasil

Re: [users@httpd] mod_proxy_hcheck response timeout?

[Daniel Ferradal]

Ahh, thanks now I understand. I appreciate your feedback.

El lun, 26 abr 2021 a las 17:48, Suvendu Sekhar Mondal
() escribió:
>
> Hello Daniel,
>
> On Mon, Apr 26, 2021 at 7:02 PM Daniel Ferradal  wrote:
> >
> > Thanks for answering
> >
> > Can you please elaborate on this?
> >
> >
> What I did was, I changed the code of the page a bit so that it throws
> an exception(in my case of type Java) after waiting for some time. In
> the real world it could be something like this:
>
> 1. Apache hits that page during health check
> 2. That page has the code which does the "real" health check of the
> target application - it could be like invoking another URL or
> something else which tells you about your app's health
> 3. After invoking that URL, it waits for x amount of time for the
> response to come before giving up. This is the alternate timeout.
> 4. If it gets a response from that URL call within x amount of time -
> then we can say that the worker is healthy, else I am throwing an
> exception which will send back HTTP 500
> 5. As Apache health check is getting 500 back, it fails that worker's
> health check
>
> During my POC, that's the only way I was able to alternatively
> simulate a health check timeout failure.
>
> Thanks!
> Suvendu
>
> > > What I found is that if I can generate an exception(say
> > > timeoutexception) after waiting for some time then the health check is
> > > failing properly and marking the worker as down. This could be the
> > > alternative option until the health check module is enhanced.
> >
> >
> > --
> > Daniel Ferradal
> > HTTPD Project
> > #httpd help at Freenode
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
> > For additional commands, e-mail: users-h...@httpd.apache.org
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
> For additional commands, e-mail: users-h...@httpd.apache.org
>


-- 
Daniel Ferradal
HTTPD Project
#httpd help at Freenode

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] Apache max workers in /server-status not same as MaxWorkers in mpm_event_module

[Rodrigo Cunha]

Hi, send the inventory this host with S/O version and Apache version.
Send the command and options used for check status.

Tks.

On Mon, Apr 26, 2021 at 10:59 AM Norbert Elbanbuena 
wrote:

> Hi,
>
> I attempted to tune Apache's configuration, and used below settings:
>
> 
> ThreadsPerChild 64
> MaxRequestWorkers 1600
> MinSpareThreads 800
> MaxSpareThreads 1600
> ServerLimit 25
> MaxConnectionsPerChild 0
> 
>
> But checking /server-status I only see Max workers up to 1152
>
> Server uptime: 11 hours 20 minutes 35 secondsServer load: 0.15 0.15 0.21Total
> accesses: 57926 - Total Traffic: 279.6 MB - Total Duration: 50642985CPU
> Usage: u35.7 s29.44 cu0 cs0 - .16% CPU load1.42 requests/sec - 7.0
> kB/second - 5060 B/request - 874.27 ms/request130 requests currently
> being processed, 1022 idle workers
> Slot PID Stopping Connections Threads Async connections
> total accepting busy idle writing keep-alive closing
> 0 22539 no 0 yes 0 64 0 0 0
> 1 22540 no 0 yes 0 64 0 0 0
> 2 22541 no 0 yes 0 64 0 0 0
> 3 22743 no 0 yes 0 64 0 0 0
> 4 22832 no 0 yes 0 64 0 0 0
> 5 22833 no 3 yes 3 61 0 0 0
> 6 22974 no 1 yes 2 62 0 0 0
> 7 22975 no 3 yes 3 61 0 0 0
> 8 22976 no 5 yes 4 60 0 0 0
> 9 22983 no 4 yes 4 60 0 0 0
> 10 23272 no 2 yes 2 62 0 0 0
> 11 23273 no 6 yes 5 59 0 0 0
> 12 23274 no 12 yes 10 54 0 1 0
> 13 23280 no 12 yes 12 52 0 0 0
> 14 23288 no 14 yes 13 51 0 0 0
> 15 23300 no 20 yes 19 45 0 0 0
> 16 23331 no 54 yes 53 11 0 0 0
> 17 23370 no 0 yes 0 64 0 0 0
> Sum 18 0 136   130 1022 0 1 0
> Am I reading it incorrectly?
>
> Regards,
>
> Norbert Elbanbuena
>


-- 
Atenciosamente,
Rodrigo da Silva Cunha
São Gonçalo, RJ - Brasil

Re: [users@httpd] Apache max workers in /server-status not same as MaxWorkers in mpm_event_module

[Norbert Elbanbuena]

So from what I understand, Apache status will display more than minimum server 
limit but will add more once spare threads is hitting the threshold.
I currently have 18 childs with 64 threads per child but I should expect to see 
more child processes spawned if there are less than 800 idle workers. Idle 
workers are spare threads identified as "_" Waiting for Connection.

Does this sound right?

Regards,

Norbert E.


From: Eric Covener 
Sent: Monday, April 26, 2021 9:27 AM
To: users@httpd.apache.org 
Subject: Re: [users@httpd] Apache max workers in /server-status not same as 
MaxWorkers in mpm_event_module



On Mon, Apr 26, 2021 at 9:53 AM Norbert Elbanbuena 
mailto:norb...@teligentip.com>> wrote:
Hi,

I attempted to tune Apache's configuration, and used below settings:


ThreadsPerChild 64
MaxRequestWorkers 1600
MinSpareThreads 800
MaxSpareThreads 1600
ServerLimit 25
MaxConnectionsPerChild 0


But checking /server-status I only see Max workers up to 1152




Server uptime: 11 hours 20 minutes 35 seconds
Server load: 0.15 0.15 0.21
Total accesses: 57926 - Total Traffic: 279.6 MB - Total Duration: 50642985
CPU Usage: u35.7 s29.44 cu0 cs0 - .16% CPU load
1.42 requests/sec - 7.0 kB/second - 5060 B/request - 874.27 ms/request
130 requests currently being processed, 1022 idle workers

I think this is showing you that there are currently 16 64-thread processes.  
The numbers might not be perfectly round because the server is not frozen while 
mod_status iterates over everything.
Apache will spin up a 17th process when there are less than 800 idle threads.

Re: [users@httpd] mod_proxy_hcheck response timeout?

[Suvendu Sekhar Mondal]

Hello Daniel,

On Mon, Apr 26, 2021 at 7:02 PM Daniel Ferradal  wrote:
>
> Thanks for answering
>
> Can you please elaborate on this?
>
>
What I did was, I changed the code of the page a bit so that it throws
an exception(in my case of type Java) after waiting for some time. In
the real world it could be something like this:

1. Apache hits that page during health check
2. That page has the code which does the "real" health check of the
target application - it could be like invoking another URL or
something else which tells you about your app's health
3. After invoking that URL, it waits for x amount of time for the
response to come before giving up. This is the alternate timeout.
4. If it gets a response from that URL call within x amount of time -
then we can say that the worker is healthy, else I am throwing an
exception which will send back HTTP 500
5. As Apache health check is getting 500 back, it fails that worker's
health check

During my POC, that's the only way I was able to alternatively
simulate a health check timeout failure.

Thanks!
Suvendu

> > What I found is that if I can generate an exception(say
> > timeoutexception) after waiting for some time then the health check is
> > failing properly and marking the worker as down. This could be the
> > alternative option until the health check module is enhanced.
>
>
> --
> Daniel Ferradal
> HTTPD Project
> #httpd help at Freenode
>
> -
> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
> For additional commands, e-mail: users-h...@httpd.apache.org
>

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] Apache max workers in /server-status not same as MaxWorkers in mpm_event_module

[Eric Covener]

On Mon, Apr 26, 2021 at 9:53 AM Norbert Elbanbuena 
wrote:

> Hi,
>
> I attempted to tune Apache's configuration, and used below settings:
>
> 
> ThreadsPerChild 64
> MaxRequestWorkers 1600
> MinSpareThreads 800
> MaxSpareThreads 1600
> ServerLimit 25
> MaxConnectionsPerChild 0
> 
>
> But checking /server-status I only see Max workers up to 1152
>



Server uptime: 11 hours 20 minutes 35 secondsServer load: 0.15 0.15 0.21Total
> accesses: 57926 - Total Traffic: 279.6 MB - Total Duration: 50642985CPU
> Usage: u35.7 s29.44 cu0 cs0 - .16% CPU load1.42 requests/sec - 7.0
> kB/second - 5060 B/request - 874.27 ms/request130 requests currently
> being processed, 1022 idle workers
>

I think this is showing you that there are currently 16 64-thread
processes.  The numbers might not be perfectly round because the server is
not frozen while mod_status iterates over everything.
Apache will spin up a 17th process when there are less than 800 idle
threads.

[users@httpd] Apache max workers in /server-status not same as MaxWorkers in mpm_event_module

[Norbert Elbanbuena]

Hi,

I attempted to tune Apache's configuration, and used below settings:


ThreadsPerChild 64
MaxRequestWorkers 1600
MinSpareThreads 800
MaxSpareThreads 1600
ServerLimit 25
MaxConnectionsPerChild 0


But checking /server-status I only see Max workers up to 1152


Server uptime: 11 hours 20 minutes 35 seconds
Server load: 0.15 0.15 0.21
Total accesses: 57926 - Total Traffic: 279.6 MB - Total Duration: 50642985
CPU Usage: u35.7 s29.44 cu0 cs0 - .16% CPU load
1.42 requests/sec - 7.0 kB/second - 5060 B/request - 874.27 ms/request
130 requests currently being processed, 1022 idle workers
SlotPID StoppingConnections Threads Async connections
total   accepting   busyidlewriting keep-alive  closing
0   22539   no  0   yes 0   64  0   0   0
1   22540   no  0   yes 0   64  0   0   0
2   22541   no  0   yes 0   64  0   0   0
3   22743   no  0   yes 0   64  0   0   0
4   22832   no  0   yes 0   64  0   0   0
5   22833   no  3   yes 3   61  0   0   0
6   22974   no  1   yes 2   62  0   0   0
7   22975   no  3   yes 3   61  0   0   0
8   22976   no  5   yes 4   60  0   0   0
9   22983   no  4   yes 4   60  0   0   0
10  23272   no  2   yes 2   62  0   0   0
11  23273   no  6   yes 5   59  0   0   0
12  23274   no  12  yes 10  54  0   1   0
13  23280   no  12  yes 12  52  0   0   0
14  23288   no  14  yes 13  51  0   0   0
15  23300   no  20  yes 19  45  0   0   0
16  23331   no  54  yes 53  11  0   0   0
17  23370   no  0   yes 0   64  0   0   0
Sum 18  0   136 130 10220   1   0

Am I reading it incorrectly?

Regards,

Norbert Elbanbuena

Re: [users@httpd] mod_proxy_hcheck response timeout?

[Daniel Ferradal]

Thanks for answering

Can you please elaborate on this?


> What I found is that if I can generate an exception(say
> timeoutexception) after waiting for some time then the health check is
> failing properly and marking the worker as down. This could be the
> alternative option until the health check module is enhanced.


-- 
Daniel Ferradal
HTTPD Project
#httpd help at Freenode

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] Monitoring httpd server performance

[Mark H. Wood]

On Sun, Apr 25, 2021 at 06:37:56PM -0400, H wrote:
> Some of you may have read or participated in solving the issue I had setting 
> up a CentOS 7 server to serve php apps requiring different php versions. This 
> is now working.
> 
> The next step is to monitor the web server, ie apache, with respect to 
> various load measurements, also access by various IP addresses etc. etc.
> 
> I know there are a variety of apps to do so but would like to solicit 
> recommendations/suggestions.

Munin does a good job for me, so far as monitoring and graphing HTTPD
accesses/unit time, traffic volume, the process pool, load times, etc.
It can also keep tabs on the utilization of hardware and a lot of other
stuff.

Nagios is good at watching for potential problems and messaging me as
needed.

For traffic analysis I usually just use Analog, and old one but good
enough for my modest needs.

Monit is useful for detecting hung or crashed services and restarting
them.

-- 
Mark H. Wood
Lead Technology Analyst

University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu


signature.asc
Description: PGP signature

[users@httpd] Apache server status shows multiple waiting for connections

[Norbert Elbanbuena]

Hi,

I have started using Apache 2.4.6 as a front for Tomcat and noticed that there 
are a lot of connections showing as "_" Waiting for Connection as identified by 
the Scoreboard key in the /server-status output. Is Apache expected to close 
these connections or is it handled by the OS, or the web application?
Is the /server-status output showing historical data for all requests processed 
by workers? Or does the information update everytime you get the stats?


Warm regards,

Norbert Elbanbuena


-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] mod_proxy_hcheck response timeout?

[Suvendu Sekhar Mondal]

Hi Daniel,

On Thu, Apr 22, 2021 at 3:50 PM Daniel Ferradal  wrote:
>
> Hello,
>
> I'm trying to examine a case in which we want a balancer member to be
> set on fail if it can't responde in specific time to the hcheck
> request
>
> This example configuration:
>
> 
> # example member 1
> BalancerMember http://ip:port/ hcmethod=HEAD hcuri=/ping hcpasses=1
> hcfails=1 hcinterval=5 timeout=5 retry=30
>
> # more realistic example member 2 and others
> BalancerMember http://ip:port/ hcmethod=HEAD hcuri=/ping hcpasses=1
> hcfails=1 hcinterval=5 timeout=60 retry=30
>
> BalancerMember http://ip:port/ hcmethod=HEAD hcuri=/ping hcpasses=1
> hcfails=1 hcinterval=5 timeout=60 retry=30
>
> BalancerMember http://ip:port/ hcmethod=HEAD hcuri=/ping hcpasses=1
> hcfails=1 hcinterval=5 timeout=60 retry=30
>
> BalancerMember http://ip:port/ hcmethod=HEAD hcuri=/ping hcpasses=1
> hcfails=1 hcinterval=5 timeout=60 retry=30
> 
>
> ProxyPass /app balancer://appbalancer/app failontimeout=on
>
> Let's assume the backend server 1 takes more than 5 seconds for the
> /ping  I would want to be set on fail and the Apache httpd server use
> the other balancermember, if there are more members in the balancer,
> for httpd to choose those other members which respond to the ping in a
> timely fashion, but in my tests, if /ping reply goes above 5 seconds,
> mod_proxy_hcheck is still saying it is ok.
>
> Is my approach correct? As with most initial approaches to a specific
> scenario, this may very well be the case... still bear with me.
>
> Right now if the backend responds to the /ping in for example, 6
> seconds, it is not being marked on fail, so as I understand any normal
> request which lasts more than 5 seconds will, I don´t need hcheck for
> that but this is just an example, there may be other more real
> scenarios like the other members I have defined
>
> for example  Balancermember 2 we set timeout 60 seconds, app takes up
> to 30-40 seconds to reply to specific requests  but suppose we have
> plenty of balancer members and may want to disable the member when it
> degrades the /ping reply to more than 10 seconds because that means it
> is getting degraded.
>
> Is it possible to set a timeout for hchecks to set a member as failed?
>
> Is my approach correct? As with most initial approaches to a specific
> scenario, this may very well be the case, which other approach do you
> suggest?
>

I quickly did a small test where I purposefully made a JSP page slower
than mod_proxy timeout value by using Thread.sleep(). Then used that
JSP in my hcuri. It looks like mod_proxy_hcheck is not using/affected
by the timeout setting - just like you found. So it looks like the
health check module does not have any timeout setting.

What I found is that if I can generate an exception(say
timeoutexception) after waiting for some time then the health check is
failing properly and marking the worker as down. This could be the
alternative option until the health check module is enhanced.

> I check there is a change coming to mod_proxy_hcheck,
> https://svn.apache.org/viewvc?view=revision=1887119, not sure
> if it applies to my case as it does not seem to mention response
> timeout, rather than checks piling up.
>
>
> Thanks in advance
>
>
>
> --
> Daniel Ferradal
> HTTPD Project
> #httpd help at Freenode
>
> -
> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
> For additional commands, e-mail: users-h...@httpd.apache.org
>

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org