Bug 72183 - Null Pointer exceptions while editing the generated model code
Summary: Null Pointer exceptions while editing the generated model code
Status: RESOLVED DUPLICATE of bug 84315
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Kent Johnson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-18 13:25 EDT by Venkat Balabhadrapatruni CLA
Modified: 2005-02-04 10:04 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Venkat Balabhadrapatruni CLA 2004-08-18 13:25:50 EDT 
After generating the model code using a Rose Model, I was editing the generated 
code, and when trying to save a change, the Eclipse 3.0 workbench hung with CPU 
pegged at 100%, and after waiting for about 15 minutes, I killed the workbench 
using Task Manager. This happened twice yesterday, I was able to bring up the 
workbench successfully after killing it using the Task list. There were some 
NullPointer Exceptions in the .log file as shown below:

!ENTRY org.eclipse.jdt.core 4 4 Aug 17, 2004 15:31:10.215
!MESSAGE Background Indexer Crash Recovery
!STACK 0
java.lang.NullPointerException: name can't be null
	at java.io.FilePermission.init(FilePermission.java:180)
	at java.io.FilePermission.<init>(FilePermission.java:253)
	at java.lang.SecurityManager.checkRead(SecurityManager.java:899)
	at java.io.FileInputStream.<init>(FileInputStream.java(Inlined Compiled 
Code))
	at org.eclipse.jdt.internal.core.index.DiskIndex.readCategoryTable
(DiskIndex.java(Compiled Code))
	at org.eclipse.jdt.internal.core.index.DiskIndex.mergeCategory
(DiskIndex.java(Compiled Code))
	at org.eclipse.jdt.internal.core.index.DiskIndex.mergeCategories
(DiskIndex.java:352)
	at org.eclipse.jdt.internal.core.index.DiskIndex.mergeWith
(DiskIndex.java:444)
	at org.eclipse.jdt.internal.core.index.Index.save(Index.java:171)
	at org.eclipse.jdt.internal.core.search.indexing.IndexManager.saveIndex
(IndexManager.java:506)
	at 
org.eclipse.jdt.internal.core.search.indexing.IndexManager.saveIndexes
(IndexManager.java:548)
	at org.eclipse.jdt.internal.core.search.indexing.IndexManager.notifyIdle
(IndexManager.java:369)
	at org.eclipse.jdt.internal.core.search.processing.JobManager.run
(JobManager.java:344)
	at java.lang.Thread.run(Thread.java:568)

!ENTRY org.eclipse.jdt.core 4 4 Aug 17, 2004 15:31:38.776
!MESSAGE Background Indexer Crash Recovery
!STACK 0
java.lang.NullPointerException: name can't be null
	at java.io.FilePermission.init(FilePermission.java:180)
	at java.io.FilePermission.<init>(FilePermission.java:253)
	at java.lang.SecurityManager.checkRead(SecurityManager.java:899)
	at java.io.FileInputStream.<init>(FileInputStream.java(Inlined Compiled 
Code))
	at org.eclipse.jdt.internal.core.index.DiskIndex.readCategoryTable
(DiskIndex.java(Compiled Code))
	at org.eclipse.jdt.internal.core.index.DiskIndex.mergeCategory
(DiskIndex.java(Compiled Code))
	at org.eclipse.jdt.internal.core.index.DiskIndex.mergeCategories
(DiskIndex.java:352)
	at org.eclipse.jdt.internal.core.index.DiskIndex.mergeWith
(DiskIndex.java:444)
	at org.eclipse.jdt.internal.core.index.Index.save(Index.java:171)
	at org.eclipse.jdt.internal.core.search.indexing.IndexManager.saveIndex
(IndexManager.java:506)
	at 
org.eclipse.jdt.internal.core.search.indexing.IndexManager.saveIndexes
(IndexManager.java:548)
	at org.eclipse.jdt.internal.core.search.indexing.IndexManager.notifyIdle
(IndexManager.java:369)
	at org.eclipse.jdt.internal.core.search.processing.JobManager.run
(JobManager.java:344)
	at java.lang.Thread.run(Thread.java:568)

At this stage I'm not really sure as to what has caused the Eclipse workbench 
to hang(I was in Java perspective), but both the times that happened, I was 
editing a generated Java class.
Comment 1 Kent Johnson CLA 2004-08-19 05:35:46 EDT 
Which VM are you using?

Is it IBM build cxia321411-20040301? If so, there are newer versions of this 
VM available - you should switch.

Suspect this is a duplicate of bug 66836
Comment 2 Kent Johnson CLA 2004-08-23 13:54:56 EDT 
Please reopen with your VM specifics.
Comment 3 Kent Johnson CLA 2005-02-04 10:03:50 EST 
same as bug 84315
Comment 4 Kent Johnson CLA 2005-02-04 10:04:08 EST 

*** This bug has been marked as a duplicate of 84315 ***