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 B9AEE198A2 for ; Wed, 20 Apr 2016 13:05:59 +0000 (UTC) Received: (qmail 66478 invoked by uid 500); 20 Apr 2016 13:05:55 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 66444 invoked by uid 500); 20 Apr 2016 13:05:55 -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 66434 invoked by uid 99); 20 Apr 2016 13:05:55 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Apr 2016 13:05:55 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 205DC18059A for ; Wed, 20 Apr 2016 13:05:55 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 5.462 X-Spam-Level: ***** X-Spam-Status: No, score=5.462 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, KAM_BADIPHTTP=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_BL=0.01, RCVD_IN_MSPIKE_L5=2.799, SPF_NEUTRAL=0.652, WEIRD_PORT=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 9HNCDshHh4tg for ; Wed, 20 Apr 2016 13:05:53 +0000 (UTC) Received: from resqmta-po-08v.sys.comcast.net (resqmta-po-08v.sys.comcast.net [96.114.154.167]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 4E9DB5F3DA for ; Wed, 20 Apr 2016 13:05:52 +0000 (UTC) Received: from resomta-po-09v.sys.comcast.net ([96.114.154.233]) by comcast with SMTP id sroraeFyH7xvbsrpAa80x4; Wed, 20 Apr 2016 13:05:44 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1461157544; bh=WJK0XtA7jQSJPpXg7+T42b59GyvRc0jR+GxA31UjKtI=; h=Received:Received:Content-Type:Mime-Version:Subject:From:Date: Message-Id:To; b=DqOCOnhg89STDsqhWsQyd3vjDSpHToJmwX7NRNZ0R6ogykBm2ow/XWHggL/h6hVH6 p+9FSTUwsfi2aDWGqoIB9AzAejAPNy0jEJwGeToGfTOIPnhNIiIwc9aoidMQU2R1KW chmIgWScUtBCQx3DQsRDrpytxiZtupfJhIrB7AkYo5y/98HRorQD0SpU9FqTcQOTA+ Y9w34lCr+0ABJVSq3v0IZonNt06fnqFlav87dlRZC0e4Jn0CCaxI5HmguqdKO50Ufk QpAwNvYTqaMenpb36yDhv8KD5YXvOS9qSLxkMbWHl0EH1ONO1I0GXIKfmpe9SLbg3u EMQs4yAfwcXIQ== Received: from [192.168.199.10] ([69.251.84.114]) by resomta-po-09v.sys.comcast.net with comcast id kd3j1s00W2U0RYt01d3jJ2; Wed, 20 Apr 2016 13:03:44 +0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: Jim Jagielski In-Reply-To: Date: Wed, 20 Apr 2016 09:03:43 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: users@httpd.apache.org X-Mailer: Apple Mail (2.3124) Subject: Re: [users@httpd] Apache ProxyPass locking all requests to balancer No, that is not expected behavior... they are not dependent at all. > On Apr 20, 2016, at 8:06 AM, Wayne W = wrote: >=20 > Hi anyone got any ideas on this? >=20 > thanks >=20 > On Mon, Apr 11, 2016 at 4:37 PM, Wayne W = wrote: > Hi, >=20 > Perhaps this is default behaviour but its not what I was expecting. I = have the following conf on Apache 2.4 >=20 > > ServerName=20 > somedomain.com >=20 > ProxyPass /share=20 > http://127.0.0.1:8181/share >=20 >=20 > ProxyPass / balancer://cluster/ stickysession=3DJSESSIONID = nofailover=3DOff >=20 > # define the balancer, with http and/or ajp connections > > Order allow,deny > Allow from all > BalancerMember ajp:// > 127.0.0.1:8010 > route=3Dg1 > BalancerMember ajp:// > 127.0.0.1:8011 > route=3Dg2 > > >=20 > With this setup I have 2 tomcat instances being load balanced and a = jetty instance which handles all requests via ProxyPass mounted to = /share >=20 > 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. >=20 > Does apache not handle this case? ie keep forwarding/load balancing = request even if one of the proxypass becomes unresponsive? >=20 >=20 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org