Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 64213 invoked from network); 2 Apr 2009 17:31:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 2 Apr 2009 17:31:06 -0000 Received: (qmail 77950 invoked by uid 500); 2 Apr 2009 17:31:00 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 77911 invoked by uid 500); 2 Apr 2009 17:31:00 -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 77884 invoked by uid 99); 2 Apr 2009 17:31:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Apr 2009 17:31:00 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of daniel.armbrust.list@gmail.com designates 74.125.92.146 as permitted sender) Received: from [74.125.92.146] (HELO qw-out-1920.google.com) (74.125.92.146) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Apr 2009 17:30:54 +0000 Received: by qw-out-1920.google.com with SMTP id 5so555748qwf.12 for ; Thu, 02 Apr 2009 10:30:33 -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 :content-transfer-encoding; bh=wSKCUaqnNKbmilbvC11LTEzPHStiwZbayyT4aP+aZMU=; b=XBTZ6S4PmuPcE3bNoxsTp5Ds1BkoFMJzYyCI3vLtW3kclJGjXJLoL03QmZz3VBNEXr fFmzF6GsPJ+/n6QMCf/anGuNK9npxA7yiHftyT9JvmDhkwQUyxtZ0fJeoDsRs8SX3FwO 9l0iuwNby1HvJ813Xm5E0zRSHtYIbOlJ02HZY= 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:content-transfer-encoding; b=GndR8Nb8bEDzchQzdVb+spuUnzvp9n6dUhKrk3IAeK0KEOERb9OFeWR8olOKeKbw/d zS71c1cZOs1Xd2ncrus1vugNwwS+E/0d5tDvsIUXxcJ2nGXABtcarWOYDc/9nW0yiTsW pkF9iuo6w+uRmDYzP+BID0kfYKXvUT5uhDYAw= MIME-Version: 1.0 Received: by 10.220.74.81 with SMTP id t17mr451875vcj.56.1238693432980; Thu, 02 Apr 2009 10:30:32 -0700 (PDT) In-Reply-To: <0AAE5AB84B013E45A7B61CB66943C17215E6EF5B6E@USEA-EXCH7.na.uis.unisys.com> References: <82f04dc40904011316x77ec9129jf4ab0daecfabf8fd@mail.gmail.com> <49D3D850.1040605@christopherschultz.net> <82f04dc40904011451h7e6e8096vcbbfe12544957ebd@mail.gmail.com> <0AAE5AB84B013E45A7B61CB66943C17215E6E3B102@USEA-EXCH7.na.uis.unisys.com> <82f04dc40904020709n2a3a4649qad4bbca55f7492b8@mail.gmail.com> <0AAE5AB84B013E45A7B61CB66943C17215E6E76DAF@USEA-EXCH7.na.uis.unisys.com> <82f04dc40904020733m1cef77d7n3e98026cc52c42f5@mail.gmail.com> <0AAE5AB84B013E45A7B61CB66943C17215E6E77070@USEA-EXCH7.na.uis.unisys.com> <82f04dc40904020828p2fb2074fq75073658b013e096@mail.gmail.com> <0AAE5AB84B013E45A7B61CB66943C17215E6EF5B6E@USEA-EXCH7.na.uis.unisys.com> Date: Thu, 2 Apr 2009 12:30:32 -0500 Message-ID: <82f04dc40904021030p14d8a42ck69889b5afa5defd5@mail.gmail.com> Subject: Re: How to debug Error: listenerStart? From: Dan Armbrust To: Tomcat Users List Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org I got a brand new copy of tomcat 5.5.25, and tested it. Some of the provided apps, such as balancer - create entries in the localhost log file. I used kdiff to compare the entire tomcat folder hierarchy to my tomcat distribution, and I can't find any significant difference that could cause my missing logs. I tried adding a missing listener to the balancer app. The error was properly logged. I tried deploying my war file (with a purposely broken listener) to the newly extracted, completely stock tomcat, and I see the same behaviour. No entries whatsoever in the localhost log file from my application, which failed to deploy. So, it would appear that something in my application - where I use log4j - is perhaps preventing the error from being logged by tomcat. What would be doing this? Something in my app is preventing this severe error from being passed up to tomcat to be logged - but then my app doesn't log it either - probably because it is stopped before it ever finishes deploying. There is obviously some interaction going on between my webapp and tomcat's logging system that I don't know about. Thanks, Dan --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org