Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 99537 invoked from network); 20 Apr 2004 16:45:50 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 20 Apr 2004 16:45:50 -0000 Received: (qmail 7990 invoked by uid 500); 20 Apr 2004 16:45:03 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 7944 invoked by uid 500); 20 Apr 2004 16:45:03 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 7907 invoked from network); 20 Apr 2004 16:45:02 -0000 Received: from unknown (HELO avocet.mail.pas.earthlink.net) (207.217.120.50) by daedalus.apache.org with SMTP; 20 Apr 2004 16:45:02 -0000 Received: from 1cust158.tnt3.barrie.on.da.uu.net ([66.48.153.158] helo=andrzej) by avocet.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 1BFyMr-0003Oh-00 for dev@cocoon.apache.org; Tue, 20 Apr 2004 09:45:06 -0700 From: "Andrzej Jan Taramina" Organization: Chaeron Corporation To: dev@cocoon.apache.org Date: Tue, 20 Apr 2004 12:44:56 -0400 MIME-Version: 1.0 Subject: SAX event stream bug under load? Reply-to: andrzej@chaeron.com Message-ID: <40851B48.21809.8FA4AAB@localhost> Priority: normal X-mailer: Pegasus Mail for Windows (v4.12a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N We've run into a situation using Cocoon 2.1.4, where under load, sometimes we seem to get wires crossed and sax event streams get mixed up between different user sessions. Or it might be some other weird concurrency bug elsewhere. Any known bugs/fixes in this area? Thanks! Andrzej Jan Taramina Chaeron Corporation: Enterprise System Solutions http://www.chaeron.com