This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 49959 - InvalidObjectException: Object with MOFID x no longer exist
Summary: InvalidObjectException: Object with MOFID x no longer exist
Status: RESOLVED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: PC Windows 3.1/NT
: P2 blocker (vote)
Assignee: issues@java
URL:
Keywords: UMBRELLA
Depends on: 48342 48508 49002 49935 50068 50088 50100 50120 50903 50974 51310
Blocks:
  Show dependency tree
 
Reported: 2004-10-05 17:22 UTC by Jan Chalupa
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Chalupa 2004-10-05 17:22:05 UTC
The information stored in the meta data storage
can occasionally get corrupted or out of sync.
This may result in InvalidObjectException errors
followed by the "Object with MOFID x no longer
exists" message. In the most severe cases, the
exceptions keep occurring frequently preventing
the user from working with the IDE.

Typically, the problem may occur after shutting
down the IDE in a non-standard way (e.g. using
Ctrl-C or the 'kill' command). However, there are
a number of reported cases of the storage getting
into an inconsistent state during normal use.

The only way around the problem is to shut down
the IDE, manually delete the meta data storage,
start again and wait until the open projects'
classpaths are scanned and the meta data recreated.

This is not an acceptable workaround. Either all
bugs resulting in the described faulty behavior
must be fixed, or a more robust and user friendly
solution has to be find for the final 4.0 release.

**************************
A workaround for NB 4.0 Beta 2 users:

1. Shut down the IDE.
2. Navigate to your userdir (usually
<home>/.netbeans/4.0beta2) and delete the content
of the var/cache/mdrstorage subfolder.
3. Start the IDE and wait until the classpath
scanning completes.

Step 2 may not be necessary. However, if the
exceptions start occurring again shortly after the
IDE is restarted, the storage must be deleted.
**************************

This is an umbrella bug. Please don't close it
until or dependent bugs are resolved, or until an
appropriate recovery mechanism is implemented.
Comment 1 Jan Becicka 2004-10-29 18:51:52 UTC
All dependent bugs fixed -> Closing
Comment 2 Quality Engineering 2007-09-20 12:44:53 UTC
Reorganization of java component