Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 2553 invoked from network); 1 Dec 2008 23:26:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Dec 2008 23:26:29 -0000 Received: (qmail 76864 invoked by uid 500); 1 Dec 2008 23:26:29 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 76834 invoked by uid 500); 1 Dec 2008 23:26:29 -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 76823 invoked by uid 99); 1 Dec 2008 23:26:29 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Dec 2008 15:26:29 -0800 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 milu71@gmx.de designates 213.165.64.20 as permitted sender) Received: from [213.165.64.20] (HELO mail.gmx.net) (213.165.64.20) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 01 Dec 2008 23:25:00 +0000 Received: (qmail invoked by alias); 01 Dec 2008 23:24:45 -0000 Received: from e178017022.adsl.alicedsl.de (EHLO wladimir) [85.178.17.22] by mail.gmx.net (mp020) with SMTP; 02 Dec 2008 00:24:45 +0100 X-Authenticated: #48488578 X-Provags-ID: V01U2FsdGVkX1/GxB5lALnGNC6erF4NGlf1poDQJKTDELew6iBO49 vRLieMTPkCUD8b Received: by wladimir (sSMTP sendmail emulation); Tue, 02 Dec 2008 00:24:39 +0000 Date: Tue, 2 Dec 2008 00:24:39 +0100 From: Michael Ludwig To: Tomcat Users List Subject: Re: Tomcat 6 unstable Message-ID: <20081201232439.GE1896@wladimir> References: <274610.84362.qm@web52807.mail.re2.yahoo.com> <0AAE5AB84B013E45A7B61CB66943C17215A3CC3817@USEA-EXCH7.na.uis.unisys.com> <20081125021846.GP1112@wladimir> <0AAE5AB84B013E45A7B61CB66943C17215A3CC3892@USEA-EXCH7.na.uis.unisys.com> <20081125222329.GC3672@wladimir> <49345441.1060405@christopherschultz.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <49345441.1060405@christopherschultz.net> User-Agent: Mutt/1.4.2.2i X-Y-GMX-Trusted: 0 X-FuHaFi: 0.6 X-Virus-Checked: Checked by ClamAV on apache.org Christopher Schultz schrieb am 01.12.2008 um 16:16:49 (-0500): > Michael Ludwig wrote: > > The very fact that object leak from one web app into another is a > > possibility seems to constitute a strong argument in favour of > > strict monitoring, be it only to shield oneself from errors that > > might be difficult to track down. > > It's rare that an object would "leak" from one app to another. When > Chuck says "more global", he means in the classloader-sense. That > typically means that the object would be passed from the webapp to the > container, which is usually a safe operation. And the object couldn't dive down into another web app because there would be a ClassCastException. > > May I rephrase this into there being a duty for the Tomcat admin to > > enforce none of the web apps loaded into his container supply a > > library that the container itself already supplies? > > That's a reasonable request, but is often easier said than done. Since > webapps can come with any variety of JAR files (or even re-packaged > JAR files) it might not be possible to enforce this rule. But, if your > webapp breaks the rules, something usually goes wrong (like a > ClassCastException) so the webapp suffers, anyway ;) Thanks for these clarifications. Michael Ludwig --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org