Return-Path: Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: (qmail 42106 invoked from network); 18 Aug 2006 15:19:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 18 Aug 2006 15:19:33 -0000 Received: (qmail 44525 invoked by uid 500); 18 Aug 2006 15:19:29 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 44470 invoked by uid 500); 18 Aug 2006 15:19:29 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 44459 invoked by uid 99); 18 Aug 2006 15:19:29 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Aug 2006 08:19:29 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [206.123.111.90] (HELO mail.loukasmgmt.com) (206.123.111.90) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Aug 2006 08:19:28 -0700 Received: (qmail 952 invoked by uid 510); 18 Aug 2006 10:19:07 -0500 Received: from unknown (HELO ?192.168.3.107?) (smtp@loukasmgmt.com@71.123.221.70) by mail.loukasmgmt.com with SMTP; 18 Aug 2006 10:19:07 -0500 Message-ID: <44E5DA78.2080606@hanik.com> Date: Fri, 18 Aug 2006 10:19:20 -0500 From: Filip Hanik - Dev Lists User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: Tomcat Developers List Subject: Re: possible mod_jk "feature" References: <8FF8B65C-0602-4727-8E3E-116506B35A55@jaguNET.com> <44E5D636.50103@apache.org> In-Reply-To: <44E5D636.50103@apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I was gonna suggest a worker..reuse=True|False This is a very minor, non intrusive change since jk_ajp_*.c already has a struct that has a reuse flag, and it respects it, the code currently hard codes it to true. so people have the option to have non persistent connections. Many folks want to use mod_jk, and don't mind the connection overhead for not reusing connections and some features like LB and *.jsp patterns are not available in httpd 1.3/2.0, so folks want jk there, so they can't switch to http. Filip Mladen Turk wrote: > Jim Jagielski wrote: >> I and other have run into issues where the socket >> between Apache and Tomcat (due to a in-between firewall) >> isn't closed as it should be... I'm digging further into >> this as far as why the timeout isn't being honored, but >> it got me thinking that a "no reuse" option might be >> nice. Basically, it prevents reuse from ever being set >> to TRUE... >> > > Makes no sense to me. > In that case user can use mod_proxy and http > protocol. AJP, or any other future protocol > like HTTP-NG/MUX > (http://www.w3.org/Protocols/HTTP-NG/Activity.html) > that is designed to be persistent would always have > to deal with badly designed firewalls. > > Anyhow, see my post about detecting the closed > socket on APR dev list. Think I'm close to the > portable solution, so this will satisfy almost > all AJP(or any persistent protocol)<->Firewall > related problems. > > Regards, > Mladen. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org > For additional commands, e-mail: dev-help@tomcat.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org