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.
This exception has been occurring for the last several weeks on new builds w/ new user dirs. I build a new IDE from source (cluster.properties=j2ee) Probably could use nightly build, I don't know, I like dogfood :o Run IDE w/ new userdir. Bring up the Tools | Options dialog. On Editor | General page, case sensitive code completion = true On Fonts/Colors | Syntax page, I select language = java, then annotation use = orange, annotation declaration = orange, parameter use = custom (purple = 153,0,204), parameter declaration = custom (purple = 153,0,204) Then I hit OK. And I get a popup box titled "Warning" that says "Editors/text/x-properties/properties.xml". I also get a java.lang.InterruptedException in the log, possibly related to saving the properties to disk (But they do appear to be saved ok.)
Created attachment 47224 [details] Snapshot of warning dialog.
Created attachment 47225 [details] stack trace (includes console messages at top as well)
Umm, seems to work fine my dev build. Anyway, could you please attach whole <userdir>/var/log/messages.log? Thanks
Created attachment 47352 [details] messages.log for the affected IDE session.
I attached the messages.log as requested. It is possible this is an artifact of an incremental build and therefore invalid, I'm not certain yet. I have seen it several times as mentioned above, but this morning I did a clean build of the same sources and cannot reproduce it. I will keep an eye out what the circumstances are that I see this if I see it again. If this is a real bug, I do not agree with the P4 priority. It is very disconcerting for the user to see exceptions during a save operation. It is reasonable to assume that corruption or other damage has occurred in such cases.
I appreciate your reasoning, but since the problem can't reliably be reproduced and there is no apparent damage done when it happens the priority is P3 at the best. I'm afraid I don't really understand what the exception means, looking at StreamPool didn't help much. The exception is thrown when reloading editor settings after saving it first and it looks like the file is still somehow locked. It also looks like that the exception is only informational, when printed the code resumes without further crash. I'm reassigning it to Filesystem guys to get some advise. Please reassign back if there is anything we should (should not) do in the editor. Thanks.
I received this error again: New clean dev build (not incremental). New user dir. Exact steps to reproduce aa originally described (except I picked a different custom color [153,0,153]). I'm running on an AMD dual core box. Could this be a race condition required two or more CPU's to reproduce?
Created attachment 47545 [details] new messages.log from 8/27 build.
This later reproduction was on JDK 5. Previous incarnations were on JDK 6, so JDK appears to be irrelevant.
the exception just says that you cannot read from stream because output stream is still open even after some delay. In other words FS ensures r/w exclusivity . Probably not closed OS
*** Issue 116909 has been marked as a duplicate of this issue. ***
Should be better now. Checking in editor/src/org/netbeans/modules/editor/options/BaseOptions.java; /cvs/editor/src/org/netbeans/modules/editor/options/BaseOptions.java,v <-- BaseOptions.java new revision: 1.155; previous revision: 1.154 done Checking in editor/libsrc/org/netbeans/editor/Settings.java; /cvs/editor/libsrc/org/netbeans/editor/Settings.java,v <-- Settings.java new revision: 1.75; previous revision: 1.74 done