Return-Path: Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 76965 invoked from network); 16 Jun 2000 20:29:57 -0000 Received: from benjamin.webslingerz.com (HELO localhost.localdomain) (206.66.49.217) by locus.apache.org with SMTP; 16 Jun 2000 20:29:57 -0000 Received: from localhost (balld@localhost) by localhost.localdomain (8.9.3/8.9.3) with ESMTP id PAA25264 for ; Fri, 16 Jun 2000 15:20:33 -0400 X-Authentication-Warning: localhost.localdomain: balld owned process doing -bs Date: Fri, 16 Jun 2000 15:20:33 -0400 (EDT) From: Donald Ball X-Sender: balld@localhost.localdomain To: cocoon-users@xml.apache.org Subject: Re: Stack overflow problem In-Reply-To: <394A2839.8C7189B8@denic.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N On Fri, 16 Jun 2000, Ulrich Mayring wrote: > Hello, > > I'm getting a stack overflow on one of my cocoon installations (Solaris, > cocoon 1.7.5dev, JServ1.1, JDK1.2.2). On other installations (namely > under Linux) I am not experiencing this problem. > > I found out that the problem lies in one of my stylesheets. I have a > recursive thing in there. It is called with a string > like "foobar", does some stuff and then calls itself with "oobar", does > some stuff and calls itself with "obar" and so on until the whole string > is "used up". > > I found if I shorten the string, then I don't get the stack overflow. > But, increasing the JVM's memory does not help - it is set to minimum 8 > MB and maximum 128 MB anyway. > > So, any suggestions how to go about this? you might try using james clark's xt processor instead and see if you still get a stack overflow. you might also try rewriting your function as a xalan extension function in java or javascript. finally, you might submit a report to the xalan guys just in case it's doing something really pathological. - donald