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 50528 - Yet more exceptions
Summary: Yet more exceptions
Status: RESOLVED FIXED
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:
: 50507 50631 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-10-17 19:58 UTC by Jesse Glick
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Stack traces (45.76 KB, text/plain)
2004-10-17 19:59 UTC, Jesse Glick
Details
More exceptions, starting with a clean cache this time (3.89 KB, text/plain)
2004-10-17 20:00 UTC, Jesse Glick
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2004-10-17 19:58:54 UTC
041015 custom. Not doing anything special, just
routine editing of some 1.5 sources. Works OK most
of the time, but sometimes some edit just triggers
a long run of exceptions for no apparent reason
and I have to shut down and delete my mdrstorage
cache.
Comment 1 Jesse Glick 2004-10-17 19:59:36 UTC
Created attachment 18342 [details]
Stack traces
Comment 2 Jesse Glick 2004-10-17 20:00:27 UTC
Hmm, even after clearing my mdrstorage cache I have some problems,
acc. to the log file anyway.
Comment 3 Jesse Glick 2004-10-17 20:00:56 UTC
Created attachment 18343 [details]
More exceptions, starting with a clean cache this time
Comment 4 Martin Matula 2004-10-18 10:03:17 UTC
*** Issue 50507 has been marked as a duplicate of this issue. ***
Comment 5 Martin Matula 2004-10-18 11:00:47 UTC
The second exception (info is null...) is a duplicate of issue 50146.
Comment 6 Martin Matula 2004-10-18 11:41:11 UTC
I was not able to identify the cause of the first set of exceptions -
maybe it was a consequence of previous errors/rollbacks. I have added
some debug output, so next time the IOE from
MetadataElement.objectChanged() is thrown, you should get also a
stacktrace of deleting the object - this should help us to identify
the root cause.

Checking in
src/org/netbeans/modules/javacore/jmiimpl/javamodel/MetadataElement.java;
/cvs/java/javacore/src/org/netbeans/modules/javacore/jmiimpl/javamodel/MetadataElement.java,v
 <--  MetadataElement.java
new revision: 1.33; previous revision: 1.32
done
Comment 7 Martin Matula 2004-10-25 16:01:45 UTC
I am not able to reproduce this. It was most likely fixed. If it
happens again, please reopen and provide the additional debug info
that should be printed out (deletion stacktrace).
Comment 8 Martin Matula 2004-10-25 17:36:43 UTC
*** Issue 50631 has been marked as a duplicate of this issue. ***
Comment 9 Quality Engineering 2007-09-20 12:49:36 UTC
Reorganization of java component