Return-Path: X-Original-To: apmail-httpd-users-archive@www.apache.org Delivered-To: apmail-httpd-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8C6731964F for ; Wed, 20 Apr 2016 12:06:50 +0000 (UTC) Received: (qmail 89841 invoked by uid 500); 20 Apr 2016 12:06:47 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 89798 invoked by uid 500); 20 Apr 2016 12:06:46 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 89784 invoked by uid 99); 20 Apr 2016 12:06:46 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Apr 2016 12:06:46 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 63C771A047D for ; Wed, 20 Apr 2016 12:06:46 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.18 X-Spam-Level: *** X-Spam-Status: No, score=3.18 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, KAM_BADIPHTTP=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, WEIRD_PORT=0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id i3P4hUhLhD0b for ; Wed, 20 Apr 2016 12:06:44 +0000 (UTC) Received: from mail-ig0-f178.google.com (mail-ig0-f178.google.com [209.85.213.178]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 801E15FB0F for ; Wed, 20 Apr 2016 12:06:43 +0000 (UTC) Received: by mail-ig0-f178.google.com with SMTP id m9so34698394ige.1 for ; Wed, 20 Apr 2016 05:06:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=L2Il5+cWiw3JQYeiO3V6O7waL2EZcvqht1n1kUj5FkM=; b=RH37yyLChtvfDvioUR6xXjR2+XJtXCVVyjnQPtwcE6nHXMQaNCBHFV/mfNaEgNjVOM DMcVcdQ9eJOxKNEhUlb+zivfh83PgdsM2kKmcysm3tuEU8dtrFHZ9IuT6Ooph7Ei8y6p QtSQeQhfrwYFyeUegk/UgqhUNQOR2yXvEy+OPEXgcAUCmVHizJAHSzxvqINVAhFw8p9b D/9ubHxGlugn+pCs7Yl9LgPNGrwiEhz379feNOpCMe4jT+xuChmX3Oxaa4gpzNaV7gjb xpX4eWM+f3SkWtTW9Ikt671ZJ5EnH/kHq/B3h0JqItZJrxeghCWx/uqHQA13LYkSEkiJ 6hWg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to; bh=L2Il5+cWiw3JQYeiO3V6O7waL2EZcvqht1n1kUj5FkM=; b=EyTBm4iTBX3Vu+zM0TVyrn/DYqjwwOvrVceGurURqd+KccyWOCtTmK5z3oizyZZGr4 E8+v5Tp+AQVzqSAq9O5p99wojurzAs+P0aJJEuZnKkMtljHVdDMXeE64lALe6lcuMhFb 5zY9wrCM0Qd2uPey6/Dcei7hlZI2vHdLEZ6zqPP6zF7Vga11p5ecSmL0nzcjzLz485IV d5/THYUuwN73xttQk0YCJdZEJHAfOS7Rk1Na9cE+Ir16gH57jXA0xQYu77XDpEDo3N87 KlelwJfxBYK83d4Fqtk4Z2rZ577vHfHFO+D99bHWN5cjD+AagrA+laRdK6ut7Gwr8gnZ hPLg== X-Gm-Message-State: AOPr4FUDVEdv4iKONeE8cVjc4y6E7VX9ivGPJCPyQQBCtOCDHoqWqKTYvQmV2ZMf8FrTLJEuOgqcgNW5tQNBZw== MIME-Version: 1.0 X-Received: by 10.50.112.98 with SMTP id ip2mr3284120igb.14.1461154002355; Wed, 20 Apr 2016 05:06:42 -0700 (PDT) Received: by 10.107.159.10 with HTTP; Wed, 20 Apr 2016 05:06:42 -0700 (PDT) In-Reply-To: References: Date: Wed, 20 Apr 2016 13:06:42 +0100 Message-ID: From: Wayne W To: users@httpd.apache.org Content-Type: multipart/alternative; boundary=047d7b41416245cc590530e96d2c Subject: [users@httpd] Re: Apache ProxyPass locking all requests to balancer --047d7b41416245cc590530e96d2c Content-Type: text/plain; charset=UTF-8 Hi anyone got any ideas on this? thanks On Mon, Apr 11, 2016 at 4:37 PM, Wayne W wrote: > Hi, > > Perhaps this is default behaviour but its not what I was expecting. I have > the following conf on Apache 2.4 > > > 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 > > Order allow,deny > Allow from all > BalancerMember ajp://127.0.0.1:8010 route=g1 > BalancerMember ajp://127.0.0.1:8011 route=g2 > > > > 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? > --047d7b41416245cc590530e96d2c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi anyone got any ideas on this?

thanks=

On Mo= n, Apr 11, 2016 at 4:37 PM, Wayne W <waynemailinglists@gmail.com= > wrote:
H= i,

Perhaps this is default behaviour but its not what I was expecting. I ha= ve 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=3DJSESSIONID nofailover=3DOf=
f

 # 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=3Dg1
      BalancerMember ajp://127.0.0.1:8011 route=3Dg2
 </Proxy>
</VirtualHost>

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

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

Does apache not handle this case? ie keep forwarding/load balancing requ= est even if one of the proxypass becomes unresponsive?


--047d7b41416245cc590530e96d2c--