httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Axel-Stéphane SMORGRAV <>
Subject RE: Apache 2.2.x: Implicit creation of new proxy_workers
Date Mon, 03 Sep 2007 06:14:31 GMT
What if the backend address is not known in the configuration because computed dynamically
using for example RewriteMap ?

In that case I cannot see any other way of doing this than creating the worker on the fly,
and unfortunately with my current modifications I sooner or later end up getting the following

[Fri Aug 31 15:32:19 2007] [emerg] (os 0x001ebf50)Unrecognized resolver error: apr_proc_mutex_lock
failed. Attempting to shutdown process gracefully.

-----Message d'origine-----
De : Plüm, Rüdiger, VF-Group [] 
Envoyé : vendredi 31 août 2007 18:20
À :
Objet : Re: Apache 2.2.x: Implicit creation of new proxy_workers

> -----Ursprüngliche Nachricht-----
> Von: Axel-Stéphane SMORGRAV
> []
> Gesendet: Freitag, 31. August 2007 16:02
> An:
> Betreff: Apache 2.2.x: Implicit creation of new proxy_workers
> Hi,
> In order for URLs proxied using RewriteRule with the P-flag to benefit 
> from proxy worker connection pools, I have

I guess there is a better way to do this. Simply use

<Proxy ajp://worker/somewhere>
   ProxySet keepalive=On

But currently this only works on trunk. The backport proposals for 2.2.x are missing one vote.
Come on guys (Mladen, Nick) please have a look :-).
There is even a documentation for ProxySet now (Thanks to Jim).



View raw message