Community
Participate
Working Groups
I do not know that it is the right place to post this error...but it is annoying me every time when i try to open some jsp , xml or java files. Try to resolve this issue and let me know why iam getting this error. An internal error occurred during: "Processing Dirty Regions". java.lang.NullPointerException Thanks koti
Can you give a full trace please? If we know what is thowing the NPE then we can route the bug correctly.
Created attachment 84543 [details] Tthis attachement is generated aumatically when the eclipse thrown exceptions
The below is the full stach trace of the Processing Dirty Regions exception !ENTRY org.eclipse.core.jobs 4 2 2007-12-03 09:51:36.606 !MESSAGE An internal error occurred during: "Processing Dirty Regions". !STACK 0 java.lang.NullPointerException at org.eclipse.wst.sse.ui.internal.reconcile.validator.ValidatorStrategy.endProcessing(ValidatorStrategy.java:138) at org.eclipse.wst.sse.ui.internal.reconcile.DocumentRegionProcessor.endProcessing(DocumentRegionProcessor.java:70) at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor.run(DirtyRegionProcessor.java:624) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) !SESSION 2007-12-03 10:27:06.030 ----------------------------------------------- eclipse.buildId=I20070625-1500 java.version=1.6.0_03 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Command-line arguments: -os win32 -ws win32 -arch x86 !ENTRY org.eclipse.core.resources 2 10035 2007-12-03 10:27:14.327 !MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes. !ENTRY org.eclipse.jst.jsp.core 4 4 2007-12-03 10:49:10.181 !MESSAGE A workspace crash was detected. The previous session did not exit normally. Not using saved taglib indexes
On which Eclipse & WTP version was this seen? It shouldn't be a problem in 2.0.1.
(In reply to comment #4) > On which Eclipse & WTP version was this seen? It shouldn't be a problem in > 2.0.1. > Iam Using Eclipse Version 3.3.0
(In reply to comment #5) > (In reply to comment #4) > > On which Eclipse & WTP version was this seen? It shouldn't be a problem in > > 2.0.1. > > > > Iam Using Eclipse Version 3.3.0 But which WTP version? I'm guessing WTP 2.0.0, in which case you should update to Eclipse 3.3.1.1 and WTP 2.0.1.