Return-Path: X-Original-To: apmail-tomcat-users-archive@www.apache.org Delivered-To: apmail-tomcat-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 7074E9073 for ; Wed, 19 Oct 2011 09:28:51 +0000 (UTC) Received: (qmail 90093 invoked by uid 500); 19 Oct 2011 09:28:48 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 89591 invoked by uid 500); 19 Oct 2011 09:28:46 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 89580 invoked by uid 99); 19 Oct 2011 09:28:41 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Oct 2011 09:28:41 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of aw@ice-sa.com designates 212.85.38.228 as permitted sender) Received: from [212.85.38.228] (HELO tor.combios.es) (212.85.38.228) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Oct 2011 09:28:35 +0000 Received: from [192.168.245.129] (p549E9227.dip0.t-ipconnect.de [84.158.146.39]) by tor.combios.es (Postfix) with ESMTPA id C4DDADA02C3 for ; Wed, 19 Oct 2011 11:28:12 +0200 (CEST) Message-ID: <4E9E980A.7050806@ice-sa.com> Date: Wed, 19 Oct 2011 11:27:38 +0200 From: =?UTF-8?B?QW5kcsOpIFdhcm5pZXI=?= Reply-To: Tomcat Users List User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Tomcat Users List Subject: Re: AJP Errors. Apache + Tomcat References: <20111019081437.M22118@gniffelnieuws.net> <4E9E8ECF.9000305@ice-sa.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Francis GALIEGUE wrote: > On Wed, Oct 19, 2011 at 10:48, André Warnier wrote: >> Hi. >> >> The problem can also be due just to the difference in startup time between >> Apache httpd and Tomcat. At the time Apache httpd (and its embedded >> mod_proxy_ajp module) try to contact Tomcat, Tomcat has possibly not yet >> "opened" its Connector on port 8009, which causes the host to refuse a >> connection to that port. >> >> In my experience anything involving Java tends to take a while to "start the >> machinery" (it is after all a "java virtual machine"). >> In the practice thus, what we always do in such configurations, is to start >> Tomcat first (which really means mostly "start the java virtual machine >> which runs Tomcat") >> , wait a couple of seconds, and then start the Apache httpd part. >> > > Actually, there is a reliable way of waiting for Tomcat to be fully > started: wait to see the port specified in open for > listening. Then you are sure Tomcat is fully loaded. This is what I > use and it's very reliable. > Yes, that would be more reliable than my 2 seconds above. Although if one really wanted to split hairs in 4 parts (lenghtwise), one could argue that the fact that the port mentioned in is open and listening, does not necessarily mean that the port in the AJP Connector is open and listening. Now just by curiosity, what mechanism do you use exactly to check that the port is listening ? (yes, the script lines..) --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org