Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 84904 invoked from network); 15 Oct 2007 20:21:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 Oct 2007 20:21:27 -0000 Received: (qmail 44760 invoked by uid 500); 15 Oct 2007 20:21:04 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 44741 invoked by uid 500); 15 Oct 2007 20:21:03 -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 44730 invoked by uid 99); 15 Oct 2007 20:21:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Oct 2007 13:21:03 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of carljmosca@gmail.com designates 209.85.128.189 as permitted sender) Received: from [209.85.128.189] (HELO fk-out-0910.google.com) (209.85.128.189) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Oct 2007 20:21:07 +0000 Received: by fk-out-0910.google.com with SMTP id f40so1774755fka for ; Mon, 15 Oct 2007 13:20:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=nMSC4fedoj5uDnJo1KBixKBwUGcX5es5vW0+u5YTsTk=; b=Yns6WYUEL9KlkwFAE+DCQNliufSBW007vx5i6216IQ+wZnE54viWDRK+Qh0yu3MMme/E1D5UgYoSPeqh6yegPqN3uDyEmF6SoNpOyiKt4topkVYpGxMWSaJGpWwOUpyW1Q1GlrEf6TyZtlbZSYtneojJ3yJw41LaTRj52jeOYK8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=hhQRpyPR++ajSR/R2Hb9WJELAAfl5yh0X7Ve+Kl6OLMkKozfg322pvlzsmOavMdszgZFadqIKWPWYKQ5N1vOEeKuvAgn0rXt5Fbgpp91RswTDWn2tk7MFNI7buMXUeNba275CcUHPLbeJ9F9gYICU1qhQRZQ+aEBPWWC3lu5A1c= Received: by 10.82.162.14 with SMTP id k14mr12011121bue.1192479645036; Mon, 15 Oct 2007 13:20:45 -0700 (PDT) Received: by 10.82.182.15 with HTTP; Mon, 15 Oct 2007 13:20:45 -0700 (PDT) Message-ID: Date: Mon, 15 Oct 2007 16:20:45 -0400 From: "Carl Mosca" To: "Tomcat Users List" Subject: Re: Dynamic logging configuration updates in Tomcat In-Reply-To: <4713C846.1050408@readytalk.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_37864_15749090.1192479645028" References: <470E6DB1.9080408@christopherschultz.net> <4713C846.1050408@readytalk.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_37864_15749090.1192479645028 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline > I've never heard of embedded Tomcat. That said, the whole deal w/ > embedded systems is that the API is drastically limited so if logging > isn't working, and this may sound like a dumb question but, is it > possible that logging just isn't supported? Yes, it's possible but not probable based on what I have read and the responses to my questions late last week. The webapps contain some generated code which does contain a few System.out.println's along with logging. I am getting the std out but I would think the logging would at least go to the default/configured logging. I get logging from the "hosting" app just fine and the web apps logging output is OK when running standalone Tomcat. Regardless, space isn't really an issue for us in that this webapp is on > it's own production quality server....unless there's a totally logical > reason to use an embedded Tomcat instance. Not an issue here either; this is more of an end-user convenience issue (the server app along with the hosted web apps are launched/updated via Java Web Start). ------=_Part_37864_15749090.1192479645028--