Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 88137 invoked from network); 2 Oct 2009 16:33:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 2 Oct 2009 16:33:28 -0000 Received: (qmail 38541 invoked by uid 500); 2 Oct 2009 16:33:24 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 38493 invoked by uid 500); 2 Oct 2009 16:33:24 -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 38482 invoked by uid 99); 2 Oct 2009 16:33:24 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Oct 2009 16:33:24 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of bocalinda@gmail.com designates 74.125.78.149 as permitted sender) Received: from [74.125.78.149] (HELO ey-out-1920.google.com) (74.125.78.149) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Oct 2009 16:33:14 +0000 Received: by ey-out-1920.google.com with SMTP id 5so251370eyb.2 for ; Fri, 02 Oct 2009 09:32:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=teDt3iuhB4qa4H/46GZBPHLecZQW3Bfvgu5ZkOG1wag=; b=FpLIvC9lnS76VgCCHWKC92UJb1yNNtKvsA3HU/R0l1cyQtFS2MGuFejj3w9FrycGBY RnMIoGnxg5fqrvHUQhmyHPM2dNUkOa0cnLKEByFPAu8NKUxq6bUvaqKXnMZ++iR4DO5f yme/hK2nk2hdBrQMA02njMOa+2V2JjB4Ow71I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=GNuLWg/nEqV3yKb8sbh1t32UGWTVhGi5UXWTuV1Zh39J5MjVPMLwimF6LgTy5+up88 Y7Y3GL4jDPdFd5gfAPX1XHvwpC5Hvj1qBIdVEeyx2Xy27udzwPsKp8xS8/mLaUOQyz0K O2jICODJy1D3yHgN5OUEmrF+y6J6EjEEx8zq4= MIME-Version: 1.0 Received: by 10.211.132.20 with SMTP id j20mr3310068ebn.32.1254501174465; Fri, 02 Oct 2009 09:32:54 -0700 (PDT) In-Reply-To: <4AC628DF.10206@hanik.com> References: <4AC628DF.10206@hanik.com> Date: Fri, 2 Oct 2009 18:32:54 +0200 Message-ID: Subject: Re: Connection between ListenerStart and clustering From: Bocalinda To: Tomcat Users List Content-Type: multipart/alternative; boundary=001636c5b2b5dfd9b60474f65026 X-Virus-Checked: Checked by ClamAV on apache.org --001636c5b2b5dfd9b60474f65026 Content-Type: text/plain; charset=ISO-8859-1 Hi Filip. I'm using version 6.0.20. You are not denying that the clustering could cause a ListenerStart Error, is that correct? 2009/10/2 Filip Hanik - Dev Lists > listenerStart error will have a stack trace in another log file depending > on what version of Tomcat you are using. > That stack trace will take out the guess work of what actually went wrong > > best > Filip > > > On 10/02/2009 10:12 AM, Bocalinda wrote: > >> Hi again, >> >> I obviously meant ListenerStart Error. >> >> >> >> 2009/10/2 Bocalinda >> >> >> >>> Hi List, >>> >>> Maybe this is a very stupid question, but I am wondering whether a >>> ListenerStart of an application could be related in any possible way to >>> problems with the Tomcat cluster? >>> >>> Thanks in advance. >>> >>> >>> >>> >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org > For additional commands, e-mail: users-help@tomcat.apache.org > > --001636c5b2b5dfd9b60474f65026--