From bloritsch@infoplanning.com Thu Aug 24 19:33:59 2000 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 15311 invoked from network); 24 Aug 2000 19:33:59 -0000 Received: from fw.infoplanning.net (HELO infoplanning.com) (@209.8.58.131) by locus.apache.org with SMTP; 24 Aug 2000 19:33:59 -0000 Received: (qmail 5874 invoked from network); 24 Aug 2000 18:37:21 -0000 Received: from minie (HELO infoplanning.com) (192.168.0.189) by inet with SMTP; 24 Aug 2000 18:37:20 -0000 Message-ID: <39A5771D.B2B60E14@infoplanning.com> Date: Thu, 24 Aug 2000 15:27:25 -0400 From: Berin Loritsch X-Mailer: Mozilla 4.72 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: more data on the SAXException problem when using xalan with cocoon References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Donald Ball wrote: > > i'm _still_ getting occasional SAXExceptions when using xalan in cocoon > under heavy load. is anyone actually interested in helping me finish the > job of tracking down and squashing this bug? > > - donald I can't help too deeply (time constraints and all). I do recall submitting a bug like this for Cocoon1/Xerces a while back. Basically, you need a new Parser for each thread. It might be the same thing--needing a new Transformer per thread.