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 50120 - Recurring InvalidObjectException in Request Processor
Summary: Recurring InvalidObjectException in Request Processor
Status: RESOLVED DUPLICATE of bug 49830
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: Sun Linux
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks: 49959
  Show dependency tree
 
Reported: 2004-10-07 19:30 UTC by nuttycombe
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 nuttycombe 2004-10-07 19:30:20 UTC
The exact conditions that cause this exception to
appear are difficult to pinpoint. In a previous
installation of NetBeans 4.0 beta 2 this exception
began occurring after a couple of days of use, the
occurrances became so frequent that the IDE became
unusable.

I reinstalled the IDE this morning and everything
was working fine until I attempted to use the "Fix
Imports" utility in the Java editor. The imports
appeared to rearrange correctly, but the IDE then
immediately threw this exception.

Annotation: Exception occurred in Request Processor
javax.jmi.reflect.InvalidObjectException: Object
with MOFID
ACE02376-1880-11D9-8C2D-C8D78399AA77:0000000000000D4C
no longer exists.
	at
org.netbeans.mdr.handlers.BaseObjectHandler._getDelegate(BaseObjectHandler.java:322)
	at
org.netbeans.mdr.handlers.BaseObjectHandler.refImmediatePackage(BaseObjectHandler.java:282)
	at
org.netbeans.mdr.util.EventNotifier$Clazz.collectListeners(EventNotifier.java:532)
	at
org.netbeans.mdr.util.EventNotifier$Instance.collectListeners(EventNotifier.java:560)
	at
org.netbeans.mdr.util.EventNotifier$Association.collectListeners(EventNotifier.java:499)
	at
org.netbeans.mdr.util.EventNotifier$Abstract.firePlannedChange(EventNotifier.java:409)
	at
org.netbeans.modules.javacore.jmiimpl.javamodel.JavaClassImpl.setSuperClass(JavaClassImpl.java:232)
	at
org.netbeans.jmi.javamodel.JavaClass$Impl.setSuperClass(Unknown
Source)
	at
org.netbeans.modules.javacore.jmiimpl.javamodel.JavaClassImpl.matchPersistent(JavaClassImpl.java:468)
	at
org.netbeans.modules.javacore.jmiimpl.javamodel.SemiPersistentElement.updatePersistent(SemiPersistentElement.java:278)
	at
org.netbeans.modules.javacore.jmiimpl.javamodel.SemiPersistentElement.matchMember(SemiPersistentElement.java:544)
	at
org.netbeans.modules.javacore.jmiimpl.javamodel.SemiPersistentElement.processMembers(SemiPersistentElement.java:440)
	at
org.netbeans.modules.javacore.jmiimpl.javamodel.ResourceImpl.matchPersistent(ResourceImpl.java:188)
	at
org.netbeans.modules.javacore.jmiimpl.javamodel.SemiPersistentElement.updatePersistent(SemiPersistentElement.java:278)
	at
org.netbeans.modules.javacore.jmiimpl.javamodel.ResourceImpl.updateMetadata(ResourceImpl.java:581)
	at
org.netbeans.modules.javacore.jmiimpl.javamodel.ResourceImpl.directUpdate(ResourceImpl.java:574)
	at
org.netbeans.modules.javacore.jmiimpl.javamodel.ResourceImpl.checkUpToDate(ResourceImpl.java:479)
	at
org.netbeans.modules.javacore.jmiimpl.javamodel.ResourceImpl.updateFromDataObject(ResourceImpl.java:385)
	at
org.netbeans.modules.javacore.ExclusiveMutex.parseIfNeeded(ExclusiveMutex.java:218)
	at
org.netbeans.modules.javacore.ExclusiveMutex.enter(ExclusiveMutex.java:137)
	at
org.netbeans.mdr.NBMDRepositoryImpl.beginTrans(NBMDRepositoryImpl.java:232)
	at
org.netbeans.modules.java.JavaEditor$2.run(JavaEditor.java:226)
	at org.openide.util.Task.run(Task.java:136)
	at
org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:330)
[catch] at
org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:686)
Comment 1 ehucka 2004-10-08 09:46:15 UTC
If the occurances are so frequent try to exit IDE and remove the
folder var/cache/mdrstorage in your userdir. It should help.

It would be nice to know some '100%' steps to reproduce this exception.
Comment 2 Martin Matula 2004-10-14 11:08:46 UTC

*** This issue has been marked as a duplicate of 49830 ***
Comment 3 Quality Engineering 2007-09-20 12:07:54 UTC
Reorganization of java component