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.
Created attachment 118600 [details] Thread dump 20120420-53323b77776c. One of the update sites in my configuration is not responding - not sure which, but probably a NetBeans site, since deadlock.netbeans.org is also not responding at the moment, so likely a network issue. Unfortunately PM seems to be loading this network content while initializing the dialog. In the meantime, all controls in the dialog are disabled, so I cannot even go to the Settings tab and try disabling that update site temporarily! I would not expect network connections to be made while the dialog is being prepared - only when the Reload Catalog button is clicked. But if you do want to trigger an automated refresh at this time, at least offer a Cancel button. And display the name of the update site being loaded in the progress bar!
Created attachment 118601 [details] Screenshot
Created attachment 118602 [details] Help > Check for Updates also hangs
Workaround is to edit relevant $userdir/config/Preferences/org/netbeans/modules/autoupdate/*.properties to say enabled=false, then restart IDE.
I guess it makes it faster - core-main/rev/834829579dbd
This seems like avoiding the problem in most cases but leaving it in less common cases. getInputSource, which I suppose is operating on cached data, should directly examine toParse.openStream() to see if it is in GZIP format. (I.e. whether it starts with \037\213, at least according to gzip-1.2.4.tar.gz!/INSTALL.) Why would it ever try to make a network connection? BTW isGzip also opens a URLConnection which it does not close, which could leak a socket.
Integrated into 'main-golden', will be available in build *201204250400* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/834829579dbd User: Jiri Rechtacek <jrechtacek@netbeans.org> Log: #211560: Unable to use Plugin Manager when one provider is hung
*** Bug 211951 has been marked as a duplicate of this bug. ***