Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 67343 invoked from network); 22 Oct 2004 20:05:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 22 Oct 2004 20:05:34 -0000 Received: (qmail 48257 invoked by uid 500); 22 Oct 2004 20:05:30 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 47985 invoked by uid 500); 22 Oct 2004 20:05:28 -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 47972 invoked by uid 99); 22 Oct 2004 20:05:27 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=NO_REAL_NAME,UPPERCASE_25_50 X-Spam-Check-By: apache.org Received: from [192.18.33.10] (HELO exchange.sun.com) (192.18.33.10) by apache.org (qpsmtpd/0.28) with SMTP; Fri, 22 Oct 2004 13:05:26 -0700 Received: (qmail 24622 invoked by uid 50); 22 Oct 2004 20:07:29 -0000 Date: 22 Oct 2004 20:07:29 -0000 Message-ID: <20041022200729.24617.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: dev@cocoon.apache.org Cc: Subject: DO NOT REPLY [Bug 31854] New: - [PATCH] Javaflow JavaInterpreter is not thread safe X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=31854 [PATCH] Javaflow JavaInterpreter is not thread safe Summary: [PATCH] Javaflow JavaInterpreter is not thread safe Product: Cocoon 2 Version: Current CVS 2.1 Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: blocks AssignedTo: dev@cocoon.apache.org ReportedBy: Ralph_Goers@dslextreme.com If a page causes two cocoon pipelines to be invoked, each of which contains javaflow, a null pointer exception may occur. This occurs because there is a race condition checking the initialized flag.