On Thu, Sep 13, 2012 at 7:33 PM, Daniel Ruggeri wrote:
>
> Does it give a unique failure code? This is actually the use case that
> drove me to add the failonstatus option for ProxySet. For example, some
> containers return a 503 when the app is not yet initialized but the
> container is up. Grant
On 9/13/2012 4:10 PM, Colin Murtaugh wrote:
> I figured that might be the case; in this situation, the timeout is
> due to the backend being slow. In particular, when I start up this
> tomcat server, it starts accepting connections quite quickly, but it
> may be 30-40 seconds before the app is ful
On Thu, Sep 13, 2012 at 2:51 PM, Jim Jagielski wrote:
>
> because these settings are stored in shared memory, post config,
> and changes made won't persist a restart or reboot since Apache
> goes back the honoring the httpd.conf file settings.
>
> If you need the updates to persist, you'll need t
On Sep 13, 2012, at 2:02 PM, Colin Murtaugh wrote:
> Hi --
>
> I'm trying to set up a pair of tomcat servers behind apache using
> mod_proxy_balancer. I'm using Apache 2.4.3 that I built a couple of days ago
> on Solaris.
>
> I see in the 2.4 docs that balancer settings can now be persiste
Hi --
I'm trying to set up a pair of tomcat servers behind apache using
mod_proxy_balancer. I'm using Apache 2.4.3 that I built a couple of days
ago on Solaris.
I see in the 2.4 docs that balancer settings can now be persistent after
restarts. I assume that this refers to changes to settings ma
