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.
Last week my computer suddenly rebooted while using NetBeans 3.4 with JDK 1.4.1. I successfully rebooted the machine, but as soon as I started NetBeans it happened again. I reinstalled the JDK and NetBeans, but found that my old settings for file systems were retained although I thought I wiped the entire install directory (Program Files\NetBeans 3.4) after uninstalling. It seems there are settings somewhere where I cannot find them. Now it has worked for a few days, but it sometimes takes a long time to start NetBeans and I get the exception included below. Even rendering the popup signaling the exception takes a long time. Today the system rebooted again when trying to execute a class in a mounted jar. Usually the reboots have no specific connection to anything I do in NetBeans. After rebooting, the system completely deadlocked after trying to do the same (mouse pointer would not move). Is is possible I have some old settings somewhere that I could wipe? Sincerely, Andreas Annotation: Cannot read class: org.openide.filesystems.JarFileSystem Annotation: Source: Mount/src#002Ezip.settings Annotation: Content: <?xml version="1.0"?> <!DOCTYPE settings PUBLIC "-//NetBeans//DTD Session settings 1.0//EN" "http://www.netbeans.org/dtds/sessionsettings- 1_0.dtd"> <settings version="1.0"> <instanceof class="org.openide.filesystems.AbstractFileSystem$Change"/> <instanceof class="org.openide.filesystems.FileSystem"/> <instanceof class="org.openide.filesystems.AbstractFileSystem$Attr"/> <instanceof class="java.io.Serializable"/> <instanceof class="java.lang.Object"/> <instanceof class="org.openide.filesystems.AbstractFileSystem"/> <instanceof class="org.openide.filesystems.AbstractFileSystem$Info"/> <instanceof class="org.openide.filesystems.JarFileSystem"/> <instanceof class="org.openide.filesystems.AbstractFileSystem$List"/> <serialdata class="org.openide.filesystems.JarFileSystem"> ACED0005737200256F72672E6F70656E6964652E66696C6573797374656 D732E4A617246696C6553797374656DFEA3640EA5 93F8870200014C0004726F6F7474000E4C6A6176612F696F2F46696C653 B7872002A6F72672E6F70656E6964652E66696C65 73797374656D732E416273747261637446696C6553797374656DD193D2E 5ABFD8BFA0300054C0004617474727400314C6F72 672F6F70656E6964652F66696C6573797374656D732F416273747261637 446696C6553797374656D24417474723B4C000663 68616E67657400334C6F72672F6F70656E6964652F66696C65737973746 56D732F416273747261637446696C655379737465 6D244368616E67653B4C0004696E666F7400314C6F72672F6F70656E696 4652F66696C6573797374656D732F416273747261 637446696C6553797374656D24496E666F3B4C00046C6973747400314C6 F72672F6F70656E6964652F66696C657379737465 6D732F416273747261637446696C6553797374656D244C6973743B4C000 87472616E736665727400354C6F72672F6F70656E 6964652F66696C6573797374656D732F416273747261637446696C65537 97374656D245472616E736665723B787200226F72 672E6F70656E6964652E66696C6573797374656D732E46696C655379737 4656D840CFB0DCFF8F9040200035A000668696464 656E4C000A6361706162696C69747974002E4C6F72672F6F70656E69646 52F66696C6573797374656D732F46696C65537973 74656D4361706162696C6974793B4C000A73797374656D4E616D6574001 24C6A6176612F6C616E672F537472696E673B7870 01737200316F72672E6F70656E6964652E66696C6573797374656D732E4 6696C6553797374656D4361706162696C69747924 4265616E08B6C4E26B7961400200045A000B636F6D70696C6174696F6E5 A000564656275675A0003646F635A000965786563 7574696F6E78700000000074001D433A5C4A6176615C6A3273646B312E3 42E305F30325C7372632E7A69707372002A6F7267 2E6F70656E6964652E66696C6573797374656D732E4A617246696C65537 97374656D24496D706CFF1123A997AF1740020001 4C000266737400274C6F72672F6F70656E6964652F66696C65737973746 56D732F4A617246696C6553797374656D3B787071 007E000B71007E001171007E001171007E0011707704000000007873720 00C6A6176612E696F2E46696C65042DA4450E0DE4 FF0300014C00047061746871007E000A787071007E000E7702005C78 </serialdata> </settings> Annotation: File C:\Java\j2sdk1.4.0_02\src.zip does not exist. org.openide.filesystems.FSException: File C:\Java\j2sdk1.4.0_02\src.zip does not exist. at org.openide.filesystems.FSException.io (FSException.java:73) at org.openide.filesystems.JarFileSystem.setJarFile (JarFileSystem.java:161) at org.openide.filesystems.JarFileSystem.readObject (JarFileSystem.java:660) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at java.io.ObjectStreamClass.invokeReadObject (ObjectStreamClass.java:824) at java.io.ObjectInputStream.readSerialData (ObjectInputStream.java:1746) at java.io.ObjectInputStream.readOrdinaryObject (ObjectInputStream.java:1646) at java.io.ObjectInputStream.readObject0 (ObjectInputStream.java:1274) at java.io.ObjectInputStream.readObject (ObjectInputStream.java:324) at org.netbeans.core.projects.XMLSettingsSupport$SettingsRecog nizer.readSerial(XMLSettingsSupport.java:420) at org.netbeans.core.projects.XMLSettingsSupport$SettingsRecog nizer.instanceCreate(XMLSettingsSupport.java:448) at org.netbeans.core.projects.SerialDataConvertor$SettingsInst ance.instanceCreate(SerialDataConvertor.java:315) at org.openide.loaders.FolderInstance.instanceForCookie (FolderInstance.java:365) at org.openide.loaders.FolderInstance$HoldInstance.instanceCre ate(FolderInstance.java:783) at org.netbeans.core.AutomountSupport.createInstance (AutomountSupport.java:83) at org.openide.loaders.FolderInstance.defaultProcessObjects (FolderInstance.java:571) at org.openide.loaders.FolderInstance.access$100 (FolderInstance.java:45) at org.openide.loaders.FolderInstance$2.run (FolderInstance.java:456) at org.openide.util.Task.run(Task.java:136) [catch] at org.openide.util.RequestProcessor$Processor.run (RequestProcessor.java:599)
Reassigne to Filesystems, again issue against mounting unexisting jar filesystem. It will be useful to warn user about impossibility to mount jar FS which doesn't exist, instead of exception. In 4.0 it will be changed and users will not mount own filesystems as we know about it know.
There is no problem in FileSystems. FSException is fired, annotated. AFAIK also in AutomountSupport was already solved. Hardly to know why computer rebooted. If deadlock, then next attache thread dumpstack to have more information.
The frequent reboot crashes were eliminated when I switched from JDK 1.4.1_01_b01 to 1.3.1_03-b03.
Can you attached thread dump? It can be showed by CTRL+Break on console.
No new info. If there is strong interest and new info, that could help to fix, then reopen.
So, marekd as WORKSFORME.
verified, closed.