Return-Path: 
 <cocoon-dev-return-38526-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 99923 invoked by uid 500); 16 Mar 2003 23:17:17 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 99908 invoked from network); 16 Mar 2003 23:17:17 -0000
Received: from pop015pub.verizon.net (HELO pop015.verizon.net)
 (206.46.170.172)
  by daedalus.apache.org with SMTP; 16 Mar 2003 23:17:17 -0000
Received: from verizon.net ([4.47.133.0]) by pop015.verizon.net
          (InterMail vM.5.01.05.27 201-253-122-126-127-20021220) with ESMTP
          id <20030316231723.PEAS14460.pop015.verizon.net@verizon.net>
          for <cocoon-dev@xml.apache.org>; Sun, 16 Mar 2003 17:17:23 -0600
Message-ID: <3E750604.7070808@verizon.net>
Date: Sun, 16 Mar 2003 15:17:24 -0800
From: Christopher Oliver <res1cf5x@verizon.net>
Reply-To: coliver@apache.org
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US;
 rv:1.0.1) Gecko/20020823 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: Eclipse JDT breaks XSP!
References: <3E74FDAA.4070809@apache.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at pop015.verizon.net from
 [4.47.133.0] at Sun, 16 Mar 2003 17:17:23 -0600
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

I didn't find anything in Eclipse bugzilla. The reports on cocoon-dev 
about this seem to all be coming from MacOS X. I glanced at the code and 
I don't see an obvious problem (look at readTable(String filename) in

http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/org.eclipse.jdt.core/compiler/org/eclipse/jdt/internal/compiler/parser/Parser.java?rev=HEAD&content-type=text/plain

The way you describe it ("randomly") makes it sound like a thread 
synchronization problem.

Since you can reproduce it, would you mind trying to debug it?

Stefano Mazzocchi wrote:
> I've been randomly experiencing empty XSP pages and the following 
> stacktrace being sent to stderr
> 
> java.lang.ExceptionInInitializerError: corrupted file parser2.rsc
>         at 
> org.eclipse.jdt.internal.compiler.parser.Parser.<clinit>(Parser.java:364)
>         at 
> org.eclipse.jdt.internal.compiler.Compiler.<init>(Compiler.java:113)
>         at 
> org.apache.cocoon.components.language.programming.java.EclipseJavaCompiler.compile(EclipseJavaCompiler.java:441) 
> 
> 
> does anybody know what's wrong?
> 
> Stefano.
> 
>