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.
[ BUILD # : 201004140201 ] [ JDK VERSION : 1.6.* ] Netbeans is stalling/freezing in an increasing patter until it just won't respond at all. Looking at the task in Task manage shows no CPU usage. When I took a look at the logs I found lots of messages like this one: WARNING [org.netbeans.core.TimableEventQueue]: too much time in AWT thread org.netbeans.core.ui.sampler.SelfSamplerAction$Controller@1845a8 INFO [org.netbeans.modules.versioning.Utils]: Utils.canWrite: java.io.File.canWrite takes too much time (8174 ms): F:\Netbeans\Outlook Interface Tester\OIT\build.xml, stacktrace: org.netbeans.modules.versioning.Utils.canWrite(Utils.java:293) org.netbeans.modules.versioning.FilesystemInterceptor.canWrite(FilesystemInterce ptor.java:108) org.netbeans.modules.masterfs.ProvidedExtensionsProxy$7.run(ProvidedExtensionsPr oxy.java:202) org.netbeans.modules.masterfs.ProvidedExtensionsProxy.runCheckCode(ProvidedExten sionsProxy.java:282) org.netbeans.modules.masterfs.ProvidedExtensionsProxy.canWrite(ProvidedExtension sProxy.java:200) I'll attach the full messages.log
Created attachment 97385 [details] Log
Jardo, could you please evaluate?
One interesting message is File.canWrite takes too much time (17363 ms): F:\Netbeans\Outlook Interface Tester\OIT\build.xml another is from Hudson module (and I think it shall be primary source of the slowness): java.io.IOException: Server rejected connection to http://system2:8080/hudson/job/OIT/68/artifact/OIT/OIT/Outlook ES Interface Tester.exe with code 505 org.netbeans.modules.hudson.api.ConnectionBuilder.doConnection(ConnectionBuilder.java:338) org.netbeans.modules.hudson.api.ConnectionBuilder.connection(ConnectionBuilder.java:227) Caused: java.io.FileNotFoundException: Server rejected connection to http://system2:8080/hudson/job/OIT/68/artifact/OIT/OIT/Outlook ES Interface Tester.exe with code 505 org.netbeans.modules.hudson.impl.RemoteFileSystem.inputStreamNoCache(RemoteFileSystem.java:325) org.netbeans.modules.hudson.impl.RemoteFileSystem.inputStream(RemoteFileSystem.java:317) I'll try to deal with this in general way in bug 181300. The rest is up to Jesse to evaluate.
"java.io.File.canWrite takes too much time (19032 ms): F:\Netbeans\Outlook Interface Tester\OIT\build.xml" - are you trying to work on projects hosted on a mapped network drive? If so, it seems that this drive is quite slow; I would strongly recommend you use only local disks for projects, and some form of version control to collaborate with colleagues. That is unrelated to the rest of this issue so I will ignore it for now; if you can reproduce a problem, please open a separate bug for it in another component. To the stack traces related to the Hudson workspace: A general solution to bug #181300 would in fact be helpful for Hudson remote workspace view. Somehow you are browsing the workspace on a Hudson job node, and the IDE is trying to guess MIME types for files it sees there. So the obvious workaround is to just not use the workspace browsing feature if the remote server is very slow and this is causing GUI freezes. (http://system2:8080/hudson/ is returning 505 "HTTP version not supported" codes, which is an unusual error; I'm not sure whether java.net.HTTPURLConnection sends HTTP 1.0 or 1.1, but a modern server should accept either without complaint. Are you using a very old web server, or a proxy server?) Normally browsing remote workspaces does not cause content to be sniffed from EQ, since the folder list is retrieved asynchronously, but it seems that on occasion FolderChildren.createNodes does in fact run synch in EQ - for jtulach to diagnose if he can. Anyway, I am trying simply throwing an IOException if any attempt is made to open an HTTP stream from EQ (formerly this was only logged as a stack trace when using -J-Dorg.netbeans.modules.hudson.api.ConnectionBuilder.level=FINER). We'll see if that helps and does not cause other problems (formerly I determined that it did but I cannot reproduce any issues at the moment): core-main #d02ab5e6d918
Now that you mention it the project is on a mapped drive. I'll move it back to local drive as the project is already working in Version control/Hudson. As for Hudson is on a Blade server with Tomcat 6.0+ I don't remember being browsing the artifacts but had the job node open and the project node open (showing the workspace folder)
Integrated into 'main-golden', will be available in build *201004170515* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/d02ab5e6d918 User: Jesse Glick <jglick@netbeans.org> Log: #184196: simply reject any attempt to make an HTTP connection from EQ. Also: if authentication is canceled for a server, do not ask again in this same session.