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 59918 - FNFE: .../*.btx (Too many open files)
Summary: FNFE: .../*.btx (Too many open files)
Status: RESOLVED DUPLICATE of bug 57975
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-14 09:08 UTC by Jesse Glick
Modified: 2005-09-05 10:05 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
messages.log from the failing IDE session (really big when uncompressed!) (143.13 KB, application/octet-stream)
2005-06-14 09:14 UTC, Jesse Glick
Details
Log from previous session, FYI (most printed exceptions are from MDR and/or javacore) (12.74 KB, application/octet-stream)
2005-06-14 09:15 UTC, Jesse Glick
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2005-06-14 09:08:43 UTC
Dev build, Mustang. I am having problems with the MDR database again. I had
opened nb_all/nbbuild and all subprojects in the previous IDE session, but
because there were various database corruptions which made Find Usages not work,
I shut down the IDE, delete $userdir/var/cache/, and restarted. This time the
scanning progress went on for a while, and then I started getting
NullPointerException's reported in the exception dialog. They kept appearing and
I could not stop them. Had to "killall java", remove the cache again, and rm
.../*OpenProjectListSettings.settings to return to normalcy.

Opening all NB modules was working for me before, but maybe there are just too
many of them now? Or perhaps more system file descriptors are being used up by
the new modules in the IDE (each open JAR is a file descriptor).

Looks to me like MDR should not be keeping a separate database file for each
source root. It just doesn't work when you need to open a lot of projects.
Comment 1 Jesse Glick 2005-06-14 09:12:16 UTC
Also, if there is a fatal I/O error when trying to open a database, MDR should
probably recover more gracefully somehow. Or javacore scanning should halt if it
encounters a database error, since it is likely that it is going to encounter a
lot more soon.
Comment 2 Jesse Glick 2005-06-14 09:14:45 UTC
Created attachment 22652 [details]
messages.log from the failing IDE session (really big when uncompressed!)
Comment 3 Jesse Glick 2005-06-14 09:15:52 UTC
Created attachment 22653 [details]
Log from previous session, FYI (most printed exceptions are from MDR and/or javacore)
Comment 4 Martin Matula 2005-07-12 17:59:10 UTC

*** This issue has been marked as a duplicate of 57975 ***