[prev in list] [next in list] [prev in thread] [next in thread] 

List:       apache-httpd-users
Subject:    [users@httpd] Re: Apache ProxyPass locking all requests to balancer
From:       Wayne W <waynemailinglists () gmail ! com>
Date:       2016-04-20 12:06:42
Message-ID: CAO9-Pr7vcZDb5nDZbJEWo2Ad2NO2=c4zsfaAgQ7u3TuzrCzgag () mail ! gmail ! com
[Download RAW message or body]

Hi anyone got any ideas on this?

thanks

On Mon, Apr 11, 2016 at 4:37 PM, Wayne W <waynemailinglists@gmail.com>
wrote:

> Hi,
>
> Perhaps this is default behaviour but its not what I was expecting. I have
> the following conf on Apache 2.4
>
> <VirtualHost *:80>
>  ServerName somedomain.com
>  ProxyPass /share http://127.0.0.1:8181/share
>
>  ProxyPass / balancer://cluster/ stickysession=JSESSIONID nofailover=Off
>
>  # define the balancer, with http and/or ajp connections
>  <Proxy balancer://cluster/>
>       Order allow,deny
>       Allow from all
>       BalancerMember ajp://127.0.0.1:8010 route=g1
>       BalancerMember ajp://127.0.0.1:8011 route=g2
>  </Proxy>
> </VirtualHost>
>
> With this setup I have 2 tomcat instances being load balanced and a jetty
> instance which handles all requests via ProxyPass mounted to /share
>
> I had an issue in production today where the jetty instance became
> unresponsive (garage collection/out of memory). However it also stopped all
> requests going to the 2 tomcat instances.
>
> Does apache not handle this case? ie keep forwarding/load balancing
> request even if one of the proxypass becomes unresponsive?
>

[Attachment #3 (text/html)]

<div dir="ltr">Hi anyone got any ideas on \
this?<div><br></div><div>thanks</div></div><div class="gmail_extra"><br><div \
class="gmail_quote">On Mon, Apr 11, 2016 at 4:37 PM, Wayne W <span dir="ltr">&lt;<a \
href="mailto:waynemailinglists@gmail.com" \
target="_blank">waynemailinglists@gmail.com</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div><div>

<p>Perhaps this is default behaviour but its not what I was expecting. I have the \
following conf on Apache 2.4</p>

<pre><code>&lt;VirtualHost *:80&gt;
 ServerName <a href="http://somedomain.com" target="_blank">somedomain.com</a>
 ProxyPass /share <a href="http://127.0.0.1:8181/share" \
target="_blank">http://127.0.0.1:8181/share</a>

 ProxyPass / balancer://cluster/ stickysession=JSESSIONID nofailover=Off

 # define the balancer, with http and/or ajp connections
 &lt;Proxy balancer://cluster/&gt;
      Order allow,deny
      Allow from all
      BalancerMember ajp://<a href="http://127.0.0.1:8010" \
                target="_blank">127.0.0.1:8010</a> route=g1
      BalancerMember ajp://<a href="http://127.0.0.1:8011" \
target="_blank">127.0.0.1:8011</a> route=g2  &lt;/Proxy&gt;
&lt;/VirtualHost&gt;
</code></pre>

<p>With this setup I have 2 tomcat instances being load balanced and a 
jetty instance which handles all requests via ProxyPass mounted to 
/share</p>

<p>I had an issue in production today where the jetty instance became 
unresponsive (garage collection/out of memory). However it also stopped 
all requests going to the 2 tomcat instances. </p>

<p>Does apache not handle this case? ie keep forwarding/load balancing request even \
if one of the proxypass becomes unresponsive?</p></div></div></div> \
</blockquote></div><br></div>



[prev in list] [next in list] [prev in thread] [next in thread]