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 67134 - IDE Generates Exception continuous after Starup with Project
Summary: IDE Generates Exception continuous after Starup with Project
Status: RESOLVED WONTFIX
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 5.x
Hardware: PC OS/2
: P4 blocker (vote)
Assignee: David Strupl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-19 16:33 UTC by folkerts
Modified: 2010-09-23 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
The first lines of the Logfile. Please note that the same Exceptions continue to occur... (47.93 KB, text/plain)
2005-10-19 16:37 UTC, folkerts
Details
dir java142 /s Output (125.84 KB, text/plain)
2005-10-19 17:14 UTC, folkerts
Details
Start of messages.log (64.02 KB, text/plain)
2006-02-04 17:27 UTC, smstog00
Details

Note You need to log in before you can comment on or make changes to this bug.
Description folkerts 2005-10-19 16:33:47 UTC
When I startup NetBeans without a Project defined I get a "5.0 I get a 

Fatal error: Repository boot/initialization failed with message: Bad Magic
Number 0 in header at offset 1.919.904.357

Exception. Hwoever, it seems I can use NetBeans despite this error.

However, when I open a new Project (or import one defined in NetBeans 4.1) I get
continous Exceptions:

org.netbeans.mdr.util.MountFailedException: Partition mount failed.

I will attach part of the Logfile from the IDE start (it's ~1.8MB large).

I start the IDE with a Program-Object created by the netbeans.cmd Script.
However, I added the "jdkhome" Parameter, so the Parameter-List is:

--os2-windowed --jdkhome C:\JAVA142

I found a Release note re. making the JRE all Upper-Case for OS/2 and did that
(both the Directories themselfes plus the Value for the jdkhome. But this didn't
help (btw: I use the same Parameters with NetBeans 4.1 which starts-up fine).

The Exceptions leave the IDE quite unusable; I set to Prio 4 as I think you
might have better things to do than looking for Problems with a Niche-OS like
OS/2...

Btw: System is eComStation 1.2 with all Fixes applied except for the Kernel
(which is still at 14.103a_W4). Java is Innoteks Java 1.4.2_05, installed to
C:\JAVA142.

If I can/should have a look into this myself pls. let me know -- after all it's
Java and I do have access to the Source!
Comment 1 folkerts 2005-10-19 16:37:06 UTC
Created attachment 26136 [details]
The first lines of the Logfile. Please note that the same Exceptions continue to occur...
Comment 2 folkerts 2005-10-19 17:13:26 UTC
Please note: I just found Bugs 60932 and 60934. The Solution there was to use a
JDK, not just a JRE. However, I do have the full JDK installed. My --jdkhome
Switch points to C:\JAVA142 for both 4.1 and 5.0. 4.1 works, 5.0 doesn't.

In case it has to do with the JDK I'll attach the "dir java142 /s" Output so you
might see a file that is missing!
Comment 3 folkerts 2005-10-19 17:14:25 UTC
Created attachment 26140 [details]
dir java142 /s Output
Comment 4 _ lcincura 2005-10-24 15:18:00 UTC
Reassigning for evaluation
Comment 5 folkerts 2005-10-24 16:41:50 UTC
Maybe this should be closed -- as it seems it's impossible to compile the
Project with Netbeans running under the Innotek SDK :-(

I tried with Netbeans 4.1 and ran into an IO Exception, sthg. with"Invalid
Handle". The "build/classes" Folder is being created, but no folder within.
After a few re-installations of eComStation, Innotek SDK and Netbeans,
re-labelling the Partitions and Moving between HPFS and JFS-Partitions I finally
found that others have exactly the same Problem with NB 4.1 and Innotek SDK;
while for me the Compile of the Netbeans-Samples worked with Innotek SDK from
within Netbeans for others even that was not possible.

As mentioned, these Problems are with NB 4.1. I just write them here because I'm
afraid that when this Bug is closed the "Invalid Handle" IO-Exception will
show-up again -- so, solving or even evaluating this will be a waste of your
ressources.

However, could you pls. note these Problems with Innotek SDK in the Readme?? I
will eMail a link to the Innotek-Support-Forum to lcincura@... because I'm not
sure if I may publicly post this...

Comment 6 smstog00 2006-02-04 17:22:09 UTC
I experience similar behavior on Windows ME, NetBeans 5.0.

Since windows.exe installer does not work on ME
(http://www.netbeans.org/issues/show_bug.cgi?id=72146), I downloaded the zip
archive.

1. extract zip
2. edit netbeans.conf, set netbeans_jdkhome="c:\Program Files\Java\jdk1.5.0_06"
3. start netbeans
4. when "scanning project classpaths" first appears in bottom right corner, the
red stop sign exception icon appears in the tray
5. click the red stop sign
-> boom! exception dialog pops up, flipping rapidly between NullPointerException
and MountFailedException

Only way to proceed is to close NetBeans with native-X close button.
NetBeans then hangs on IDE Shutdown: "Writing project classpath information to
persistent storage."
Comment 7 smstog00 2006-02-04 17:27:14 UTC
Created attachment 28753 [details]
Start of messages.log
Comment 8 smstog00 2006-02-04 17:29:39 UTC
? I wonder if this issue is related to
http://www.netbeans.org/issues/show_bug.cgi?id=59076
Comment 9 David Strupl 2010-09-23 09:14:32 UTC
I am closing all reports in category Java/Unsupported as wontfix. These should
be dead issues --- if the reported cases are against some live part of the
NetBeans IDE please reopen and we can discuss to which category they belong.