Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org Received: (qmail 19740 invoked from network); 6 Nov 2004 20:41:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 6 Nov 2004 20:41:46 -0000 Received: (qmail 81725 invoked by uid 500); 6 Nov 2004 20:41:13 -0000 Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 81672 invoked by uid 500); 6 Nov 2004 20:41:12 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 81652 invoked by uid 99); 6 Nov 2004 20:41:12 -0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=PRIORITY_NO_NAME,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of jak-tomcat-user@m.gmane.org designates 80.91.229.2 as permitted sender) Received: from [80.91.229.2] (HELO main.gmane.org) (80.91.229.2) by apache.org (qpsmtpd/0.28) with ESMTP; Sat, 06 Nov 2004 12:41:11 -0800 Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1CQXMy-0000HR-00 for ; Sat, 06 Nov 2004 21:41:08 +0100 Received: from lsanca1-ar58-4-7-180-163.lsanca1.dsl-verizon.net ([4.7.180.163]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 06 Nov 2004 21:41:08 +0100 Received: from wbarker by lsanca1-ar58-4-7-180-163.lsanca1.dsl-verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 06 Nov 2004 21:41:08 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: tomcat-user@jakarta.apache.org From: "Bill Barker" Subject: Re: AJP in tomcat 5.x Date: Sat, 6 Nov 2004 12:41:13 -0800 Lines: 33 Message-ID: References: <0B9B46717C8FF349AFD7A069A4BB5F6438F8F8@cernxchg20.cern.ch> X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: lsanca1-ar58-4-7-180-163.lsanca1.dsl-verizon.net X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-RFC2646: Format=Flowed; Original Sender: news X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N 1) The development branch of httpd (slated to be released as httpd 2.2) contains an ajp13 module that works under mod_proxy. I've heard that it is possible to build the v2.2 mod_proxy against httpd 2.0, but it is unlikely to be included in an official v2.0 release. 2) It's not a typo. While it is possible to use mod_jk2 with 5.5, mod_jk2 is currently unmaintained. The page is only mentioning the maintained native connectors so that people won't expect that mod_jk2 bugs will ever be fixed. :) "Michal Kwiatek" wrote in message news:0B9B46717C8FF349AFD7A069A4BB5F6438F8F8@cernxchg20.cern.ch... Hello All, AJP connector documentation for tomcat 5.5 (http://jakarta.apache.org/tomcat/tomcat-5.5-doc/config/ajp.html) reads: The native connectors supported with this Tomcat release are: - JK 1.2.x with any of the supported servers - mod_proxy on Apache httpd 2.x (included by default in Apache HTTP Server 2.2), with AJP enabled Hence my questions: - what is a "mod_proxy with AJP enabled"? Too my understanding, mod_proxy has nothing to do with AJP. Or does it? - why does it say "JK 1.2.x"? What about JK2? Is it a typo and both can be used with Tomcat 5.5, or what? And which one (JK 1.2.x or JK2) is recommended? Thank you in advance, Michal. --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org