Return-Path: 
 <cocoon-users-return-28961-apmail-xml-cocoon-users-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org
Received: (qmail 40727 invoked by uid 500); 15 Feb 2002 00:24:45 -0000
Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-users-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-users-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-users@xml.apache.org>
Reply-To: cocoon-users@xml.apache.org
Delivered-To: mailing list cocoon-users@xml.apache.org
Received: (qmail 40715 invoked from network); 15 Feb 2002 00:24:45 -0000
X-Authentication-Warning: vasquez.zip.com.au: Host bluetoad.zip.com.au
 [61.8.7.100] claimed to be harmony.bluetoad.com.au
From: Peter Schwenke <peter@bluetoad.com.au>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15468.21840.915237.48323@harmony.bluetoad.com.au>
Date: Fri, 15 Feb 2002 10:24:48 +1000
To: cocoon-users@xml.apache.org
Subject: OutOfMemoryError and xsp file size
In-Reply-To: <3C6C4EFB.3273C58B@myra.com>
References: <3C6C4EFB.3273C58B@myra.com>
X-Mailer: VM 6.92 under Emacs 20.7.1
Reply-To: peter@bluetoad.com.au
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N


If the size of the XSP isn't that big that it is a design issue you
might just want to increase the heap size of your JVM.  

You can set the min/max heap sizes using parameters such as 

-ms128m -mx256m

(depending on your JVM)

                                                        ...Peter
Steve Switzer writes:
 > I'm getting the following error when I execute my
 > xsp:
 > 
 > 500 Servlet Exception
 > java.lang.OutOfMemoryError
 > <<no stack trace available>>
 > 
 > I'm using Resin 2.0.5 and Cocoon 2.0
 > 
 > A former co-worker told me, at one time, that my problem
 > was that my xsp file was too big.  By reducing it's size I used
 > to be able to get past the out of memory error -- the error was
 > always intermittent, depending on the data being picked up by
 > the sql in the xsp.  Well now the error is back, and the users
 > actually want to start using this xsp!! (They didn't care before.)
 > 
 > The former co-worker at the time suggested that the real solution
 > was not to keep reducing the size of the xsp file, but that it was
 > an architectural issue.
 > 
 > Any comments or solutions?
 > 
 > Thanks, Steve Switzer.
 > 
 > 
 > ---------------------------------------------------------------------
 > Please check that your question has not already been answered in the
 > FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
 > 
 > To unsubscribe, e-mail: <cocoon-users-unsubscribe@xml.apache.org>
 > For additional commands, e-mail: <cocoon-users-help@xml.apache.org>

---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

To unsubscribe, e-mail: <cocoon-users-unsubscribe@xml.apache.org>
For additional commands, e-mail: <cocoon-users-help@xml.apache.org>