can't startup 929 (null pointer exceptions)

Hello,

I upgraded from 922 to 929 (the only modifications) to the project were turning off all inspections.
I also have about 250 files (130 java files in a normal naming convention java package directory gov.mtc....beans...etc, and 120 or so JSP files in an HTML directory)

It asked me to convert the project file, then proceed to give me an error dialog box that said I needed to exit IDEA.

Also: we purchased the IDEA product, and I found that the 3.x were buggy with memory leaks and I had to constantly reboot intellij, so I upgraded to the EAP (929 wasn't bad, but had problems plus memory leaks again, so I upgraded to 929, and now can't run the product at all).
Question: is there a stable version at this point we can use? I have deadlines and I can't keep rebooting my IDE.

For the current problem on the java console was the following:


ERROR - intellij.plugins.PluginManager -
ERROR - intellij.plugins.PluginManager - IntelliJ IDEA (Aurora) Bui
ld #929
ERROR - intellij.plugins.PluginManager - JDK: 1.4.2
ERROR - intellij.plugins.PluginManager - VM: Java HotSpot(TM) Client
VM
ERROR - intellij.plugins.PluginManager - Vendor: Sun Microsystems Inc
.
ERROR - intellij.plugins.PluginManager - OS: Windows XP
ERROR - intellij.plugins.PluginManager - Last Action:
ERROR - intellij.plugins.PluginManager -
java.lang.NullPointerException
at com.intellij.psi.impl.e.e.b(e.java:116)
at com.intellij.psi.impl.e.e.processDeclarations(e.java:76)
at com.intellij.psi.scope.h.a(h.java:50)
at com.intellij.psi.impl.source.jsp.bc.a(bc.java:304)
at com.intellij.psi.impl.source.jsp.bc.processDeclarations(bc.java:212)
at com.intellij.psi.scope.h.a(h.java:50)
at com.intellij.psi.scope.h.a(h.java:126)
at com.intellij.psi.impl.source.f.a.a.b.d.a(d.java:3)
at com.intellij.psi.impl.source.f.a.a.b.e.a(e.java:7)
at com.intellij.psi.impl.source.f.a.a.c.a(c.java:1)
at com.intellij.psi.impl.source.f.a.a.c.resolve(c.java:0)
at com.intellij.codeInsight.d.a.b.t.visitJspAttributeValue(t.java:85)
at com.intellij.psi.impl.source.jsp.u.accept(u.java:2)
at com.intellij.codeInsight.d.a.b.r.visitJspElement(r.java:194)
at com.intellij.psi.JavaElementVisitor.visitJspAttributeValue(JavaElemen
tVisitor.java:53)
at com.intellij.psi.impl.source.jsp.u.accept(u.java:2)
at com.intellij.codeInsight.d.a.b.r.a(r.java:493)
at com.intellij.codeInsight.d.a.bg.a(bg.java:46)
at com.intellij.codeInsight.d.a.bg.a(bg.java:47)
at com.intellij.codeInsight.d.a.cn.run(cn.java:8)
at com.intellij.openapi.application.a.d.runReadAction(d.java:240)
at com.intellij.codeInsight.d.a.da.a(da.java:19)
at com.intellij.codeInsight.d.a.da.b(da.java:10)
at com.intellij.codeInsight.d.a.cm.run(cm.java:3)
at com.intellij.progress.c.a(c.java:4)
at com.intellij.codeInsight.d.a.da.run(da.java:13)

7 comments
Comment actions Permalink

IDEA 3.x is stable and perfectly fit for production work.

It seems you have lots of JSP files in your project. The jasper JSP compiler has a well know bug that leaks memory -- a bug not related to IDEA at all, as far as I know. Try do do the following: disable JSP validation on build and use jikes for compiling, instead of javac. This should help with your memory problems.

About the 929 exceptions, try cleaning up all your caches (go to "C:\Documents and Settings\yourusername\.IntelliJIDEA\system") and delete everything there exception the license file. If you're on *nix, that should be ~/.IntelliJIDEA/system. If this doesn't help either, fill a bug request.

0
Comment actions Permalink

Hello,

Thanks for the suggestions.

I don't do any JSP compilation in IDEA... it is done
by the servlet container. Are you saying the JSP compiler that is shipped with IDEA (jasper) is used to determine syntax violations, and that has memory leaks?

If so, why doesn't IntelliJ ship a jasper compiler that is patched? or patch it yourselves (it is open source).

RE: 929, thanks That fixed the problem.

-Joel

0
Comment actions Permalink

OOops that didn't fix the problem - it showed up again shortly (within 10-15minutes) of editing my JSP files. I don't recall doing anything in particular to trigger the NPE, but perhaps it was doing a syntax check or something like that....

Anyhow 929 is still a problem (apparently the same problem?) for me.

-Joel

0
Comment actions Permalink

Can you recommend something else?

Is 930 out soon?

Thanks,
Joel

0
Comment actions Permalink

Nope, no other suggestions... what's worse, this bug now is biting me too. I hope there's a new build soon!

0
Comment actions Permalink

That is a known bug with jsps that have a <jsp:useBean /> tag. Can't seem
to find it in the tracker but I believe it's fixed in 930 which should be
out soon.

"Joel" <no_mail@jetbrains.com> wrote in message
news:2468671.1064090385474.JavaMail.itn@is.intellij.net...

OOops that didn't fix the problem - it showed up again shortly (within

10-15minutes) of editing my JSP files. I don't recall doing anything in
particular to trigger the NPE, but perhaps it was doing a syntax check or
something like that....
>

Anyhow 929 is still a problem (apparently the same problem?) for me.

>

-Joel



0
Comment actions Permalink

Hi Marcus,

Can you comment on the memory leaks?:

I don't do any JSP compilation in IDEA... it is done
by the servlet container. Are you saying the JSP
compiler that is shipped with IDEA (jasper) is used to
determine syntax violations, and that has memory leaks?


Thanks,
Joel

0

Please sign in to leave a comment.