You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Stefano Mazzocchi <st...@apache.org> on 2003/03/16 23:41:46 UTC

Eclipse JDT breaks XSP!

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.


Re: Eclipse JDT breaks XSP!

Posted by Stuart Roebuck <st...@mac.com>.
I've just tried the 2.1 release of jdt_core and this appears to solve  
the Mac OS X issues with C2.1.  How about updating the CVS version to  
2.1?

Stuart.

On Monday, March 17, 2003, at 01:01  pm, Stefano Mazzocchi wrote:

> Christopher Oliver wrote:
>> Found it:
>> http://bugs.eclipse.org/bugs/show_bug.cgi?id=34658#c28
>
> ah, that also explains some random problems I'm experiencing with  
> Eclipse... it appears to be a problem with the JDK 1.4.1 macosx  
> implementation of InputStream.available() which is a native function.
>
> Wow, this really shows that Java portability is really a matter of a  
> single JVM codebase rather than java itself.
>
>
            Public Key - 1024D/88DD65AF 2001-11-23 Stuart Roebuck  
(Adolos)
      Key fingerprint = 89D9 E405 F8B1 9B22 0FA2  F2C1 9E57 5AB1 88DD  
65AF
------------------------------------------------------------------------ 
-
Stuart Roebuck                                   
stuart.roebuck@adolos.com
Systems Architect                             Java, XML, MacOS X, XP,  
etc.
ADOLOS                                            
<http://www.adolos.com/>


Re: Eclipse JDT breaks XSP!

Posted by Stefano Mazzocchi <st...@apache.org>.
Christopher Oliver wrote:
> Found it:
> http://bugs.eclipse.org/bugs/show_bug.cgi?id=34658#c28

ah, that also explains some random problems I'm experiencing with 
Eclipse... it appears to be a problem with the JDK 1.4.1 macosx 
implementation of InputStream.available() which is a native function.

Wow, this really shows that Java portability is really a matter of a 
single JVM codebase rather than java itself.


Re: Eclipse JDT breaks XSP!

Posted by Christopher Oliver <re...@verizon.net>.
Found it:
http://bugs.eclipse.org/bugs/show_bug.cgi?id=34658#c28


Pier Fumagalli wrote:
> On 16/3/03 23:40, "Vadim Gritsenko" <va...@verizon.net> wrote:
> 
>>Christopher Oliver wrote:
>>
>>
>>>I didn't find anything in Eclipse bugzilla. The reports on cocoon-dev
>>>about this seem to all be coming from MacOS X.
>>
>>It works ok under Win, so it should be platform related issue.
> 
> 
> It is ... Eclipse on OS/X is still alpha and damn slow, unfortunately.
> 
>     Pier
> 
> 



Re: Eclipse JDT breaks XSP!

Posted by Pier Fumagalli <pi...@betaversion.org>.
On 16/3/03 23:40, "Vadim Gritsenko" <va...@verizon.net> wrote:
> Christopher Oliver wrote:
> 
>> I didn't find anything in Eclipse bugzilla. The reports on cocoon-dev
>> about this seem to all be coming from MacOS X.
> 
> It works ok under Win, so it should be platform related issue.

It is ... Eclipse on OS/X is still alpha and damn slow, unfortunately.

    Pier


Re: Eclipse JDT breaks XSP!

Posted by Vadim Gritsenko <va...@verizon.net>.
Christopher Oliver wrote:

> I didn't find anything in Eclipse bugzilla. The reports on cocoon-dev 
> about this seem to all be coming from MacOS X. 


It works ok under Win, so it should be platform related issue.

Vadim


> 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. 
>



Re: Eclipse JDT breaks XSP!

Posted by Christopher Oliver <re...@verizon.net>.
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.
> 
>