Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 52320 invoked from network); 13 Apr 2000 21:28:58 -0000 Received: from mta1.rcsntx.swbell.net (151.164.30.25) by locus.apache.org with SMTP; 13 Apr 2000 21:28:58 -0000 Received: from [209.184.0.41] by mta1.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FSZ000H44ZPP9@mta1.rcsntx.swbell.net> for cocoon-dev@xml.apache.org; Thu, 13 Apr 2000 16:28:38 -0500 (CDT) Date: Thu, 13 Apr 2000 16:28:36 -0500 From: Mike Engelhart Subject: Re: XSP size limit?? In-reply-to: <20000413124420.80187.qmail@hotmail.com> To: cocoon-dev@xml.apache.org Message-id: MIME-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Robin Green wrote: > > Tut, tut, you didn't specify your Cocoon version! :) > > Anyway, a little trick I often use when a program hangs for ages is to get > it to display a stack trace. With Sun's Solaris JVM this is done by sending > a SIGQUIT to the VM, which is either CTRL+\ if it is a foreground process on > the current terminal, or > > kill -QUIT x > > where x is the pid of the java process, if it is a background process (as > yours probably would be). > > I know you can do it in Linux Blackdown with a CTRL+\ if it is in the > foreground. Don't know about the IBM JDK. > > Unfortunately this doesn't always work, and isn't always helpful. E.g. bad > FTP connections screw it up. But it's worth a try. > > Sounds like an IBM compiler bug to me, at a guess. Well, I'm having the same problem with the Sun JDK 1.2.2 and also on the MacOS JVM. Has anyone used XSP to compile a medium sized XML file with a big chunk of static data?? I think this is looking like a bug in the XSP implementation although I'm in crunch right now and can't dig into what might be causing it. I started removing elements from the XML document and after removing about 1/3 of them, it compiles....sounds fishy to me. Mike