Re: cyclic exception nesting infinite loop

Hi Peter,
the exception is thrown because the Parser is not able to determine the
boot classpath, this is caused either because the parsed file is not in
a project or because of bug in the classpath implementation.
To determine which case is the true, I need to know more details.

Is the Java file displayed under the Packages node?

Isn't the project already closed?

Does the compilation work?

How does the boot classpath look like (Customizer of
Project/Output/Compiled Classes node)?

Tomas

On Mon, 2003-07-28 at 22:13, Peter Wisnovsky wrote:
> I'm trying to convert a module that built on the Java module to the
> Projects APIs. I'm getting a problem with a null pointer exception:
> 
> *********** Exception occurred ************ at Mon Jul 28 13:02:29 PDT 2003
> Annotation: Parser error
> java.lang.NullPointerException
> 	at org.netbeans.modules.java.gj.V8ClassReader.setBootClassPath(V8ClassReader.java:244)
> 	at org.netbeans.modules.java.gj.V8EngineBase.setSearchPaths(V8EngineBase.java:162)
> 	at org.netbeans.modules.java.gj.JavaParserEngine.getEngine(JavaParserEngine.java:100)
> 	at org.netbeans.modules.java.gj.JavaParserEngine.process(JavaParserEngine.java:70)
> 	at org.netbeans.modules.java.parser.ParsingSupport$Processor.process(ParsingSupport.java:703)
> 	at org.netbeans.modules.java.parser.ParsingSupport$Processor.parseLockModel(ParsingSupport.java:654)
> [catch] at org.netbeans.modules.java.parser.ParsingSupport$Processor.run(ParsingSupport.java:585)
> 	at org.openide.util.Task.run(Task.java:136)
> 	at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:330)
> 	at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:677)
> ==>
> WARNING - ErrorManager detected cyclic exception nesting:
> 	java.lang.NullPointerException
> Be sure not to annotate an exception with itself, directly or indirectly.
> *********** Exception occurred ************ at Mon Jul 28 13:02:29 PDT 2003
> Annotation: Parser error
> java.lang.NullPointerException
> 	at org.netbeans.modules.java.gj.V8ClassReader.setBootClassPath(V8ClassReader.java:244)
> 	at org.netbeans.modules.java.gj.V8EngineBase.setSearchPaths(V8EngineBase.java:162)
> 	at org.netbeans.modules.java.gj.JavaParserEngine.getEngine(JavaParserEngine.java:100)
> 	at org.netbeans.modules.java.gj.JavaParserEngine.process(JavaParserEngine.java:70)
> 	at org.netbeans.modules.java.parser.ParsingSupport$Processor.process(ParsingSupport.java:703)
> 	at org.netbeans.modules.java.parser.ParsingSupport$Processor.parseLockModel(ParsingSupport.java:654)
> [catch] at org.netbeans.modules.java.parser.ParsingSupport$Processor.run(ParsingSupport.java:585)
> 	at org.openide.util.Task.run(Task.java:136)
> 	at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:330)
> 	at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:677)
> ==>
> WARNING - ErrorManager detected cyclic exception nesting:
> 	java.lang.NullPointerException
> Be sure not to annotate an exception with itself, directly or indirectly.
> *********** Exception occurred ************ at Mon Jul 28 13:02:29 PDT 2003
> 
> ...ad infinitum.
> 
> It then appears to be in an infinite loop of these messages, but only
> if my module is enabled...now, my module does attempt to use the src
> tree, so perhaps there is a novel race condition here. In any caseI
> can't figure out what the problem is among all these thousands of
> identical exceptions. The source is simply:
> 
>     package ws;
> 
>     public class WS
>     {
>     }
> 
> At the very least it seems like there is a problem with the handler
> kicking off a new parse process regardless of how the previous one
> failed.
> 
> Peter
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>