Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 89240 invoked from network); 26 Feb 2008 06:56:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Feb 2008 06:56:15 -0000 Received: (qmail 85209 invoked by uid 500); 26 Feb 2008 06:56:08 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 85126 invoked by uid 500); 26 Feb 2008 06:56:08 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: users@cocoon.apache.org List-Id: Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 85115 invoked by uid 99); 26 Feb 2008 06:56:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Feb 2008 22:56:08 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.9] (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 26 Feb 2008 06:55:42 +0000 Received: (qmail 89109 invoked from network); 26 Feb 2008 06:55:51 -0000 Received: from localhost (HELO carsten-ziegelers-computer.local) (127.0.0.1) by localhost with SMTP; 26 Feb 2008 06:55:51 -0000 Message-ID: <47C3B7F7.7040603@apache.org> Date: Tue, 26 Feb 2008 07:55:51 +0100 From: Carsten Ziegeler User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; de; rv:1.8.1.9) Gecko/20071031 Thunderbird/2.0.0.9 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: users@cocoon.apache.org Subject: Re: jetty References: <47C29EBF.3040109@cc.oulu.fi> In-Reply-To: <47C29EBF.3040109@cc.oulu.fi> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Which xml files are you refering to? Carsten Andre Juffer wrote: > Hi All, > > I am testing a cocoon-based webapp. For this, I use the 'mvn jetty:run'. > This all works fine, unless there is an error in any of the underlying > XML files. For instance, if there is a minor error like missing an '>' > (implying invalid XML), which is just a typing error, jetty just hangs > up completely and ultimately gives an out of memory error exception. If > that is not the case, the only way to stop jetty is to manually kill the > process (on a Linux box). Is there a way to get rid of or change this > behavior. With cocoon 2.1.* (and tomcat), decent error message and stack > trace were returned so that could figure out the problem. This would be > the preferred behavior. > > Thanks, > Andre > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org > For additional commands, e-mail: users-help@cocoon.apache.org > > -- Carsten Ziegeler cziegeler@apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org