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 47239 - InvalidObjectException after opening file
Summary: InvalidObjectException after opening file
Status: RESOLVED WORKSFORME
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Martin Matula
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-16 08:14 UTC by pfelenda
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Java file (435 bytes, text/plain)
2004-08-16 08:15 UTC, pfelenda
Details
InvalidObjectException (1.83 KB, text/plain)
2004-08-16 08:16 UTC, pfelenda
Details
Stack trace (8.26 KB, text/plain)
2004-08-16 08:17 UTC, pfelenda
Details

Note You need to log in before you can comment on or make changes to this bug.
Description pfelenda 2004-08-16 08:14:54 UTC
Steps to reproduce:
- open the attached file File|Open File
-> The exception appeared and stacke trace in
system cosole appeared

--- tail of exception ---

javax.jmi.reflect.InvalidObjectException: Object
with MOFID
A7D97544-EF52-11D8-AAC4-24A33B95AA77:000000000000104D
no longer exists.
	at
org.netbeans.mdr.handlers.BaseObjectHandler._getDelegate(BaseObjectHandler.java:322)
Comment 1 pfelenda 2004-08-16 08:15:26 UTC
Created attachment 16826 [details]
Java file
Comment 2 pfelenda 2004-08-16 08:16:05 UTC
Created attachment 16827 [details]
InvalidObjectException
Comment 3 pfelenda 2004-08-16 08:17:26 UTC
Created attachment 16828 [details]
Stack trace
Comment 4 Martin Matula 2004-08-16 09:10:45 UTC
What build were you running with?
Comment 5 pfelenda 2004-08-16 09:12:10 UTC
I forgot.
The build is 200408151800.
Comment 6 Pavel Flaska 2004-09-16 12:24:44 UTC
In your file, there is not opening /* comment at the beginning. It
leads to situation, that scanning of file does not register the class
to index. When you start editing of the file, MDRParser is able to
recover from the error state but he does not get the classindex item.
Then the class is added (reason of exception). Now, the information is
logged only to messages.log, not to bother user with this. (it is not
critical problem, the state is recovered.)
Note: in dev builds, the stacktrace is also printed to console.
Comment 7 Pavel Flaska 2004-09-16 12:26:29 UTC
In current builds, you should get only this exception in log and
stacktrace, no exception in dialog or other window.
Marking is WORKSFORME, if you are able to reproduce any incorrect
behaviour, please, reopen it.

[catch]java.lang.Exception: Class not found in index: Main. Recovering...
        at
org.netbeans.modules.javacore.parser.MDRParser.resolveSuperTypes(MDRParser.java:1148)
        at
org.netbeans.modules.javacore.parser.MDRParser.processAST(MDRParser.java:327)
        at
org.netbeans.modules.javacore.parser.MDRParser.processAST(MDRParser.java:293)
        at
org.netbeans.modules.javacore.parser.MDRParser.processAST(MDRParser.java:270)
        at org.netbeans.modules.javacore.p[catch]java.lang.Exception:
Class not found in index: Main. Recovering...
        at
org.netbeans.modules.javacore.parser.MDRParser.resolveSuperTypes(MDRParser.java:1148)
        at
org.netbeans.modules.javacore.parser.MDRParser.processAST(MDRParser.java:327)
        at
org.netbeans.modules.javacore.parser.MDRParser.processAST(MDRParser.java:293)
        at
org.netbeans.modules.javacore.parser.MDRParser.processAST(MDRParser.java:270)
        at
org.netbeans.modules.javacore.parser.MDRParser.enterMembers(MDRParser.java:210)
arser.MDRParser.enterMembers(MDRParser.java:210)
Comment 8 Quality Engineering 2007-09-20 12:18:44 UTC
Reorganization of java component