Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 84978 invoked by uid 500); 17 Apr 2002 16:25:47 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 84967 invoked from network); 17 Apr 2002 16:25:46 -0000 Subject: How bad is a Transformer "Fatal Error"? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Wed, 17 Apr 2002 18:23:11 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message Message-ID: <84F0A43A4248CE45B5C0E20F4C40779C0C0DE1@naomi.webworks.nl> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: How bad is a Transformer "Fatal Error"? Thread-Index: AcHmLCqOEdEbHh4lSyisXG6PYP/NLg== From: =?iso-8859-1?Q?Arj=E9_Cahn?= To: X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N When a transformer outputs a "Fatal Error", will this make Cocoon = instable? I have the feeling that several Fatal's in a row fill up Tomcat's = memory. Regards, Arj=E9 Cahn --------------------------------------------------------- Content Management Department Hippo Webworks Grasweg 35 1031 HW Amsterdam The Netherlands Tel +31 (0)20 6345173=20 Fax +31 (0)20 6345179 arje(at)hippo(dot)nl / www.hippo.nl --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org