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.
Module "Netbeans Plugin Development" wants to be updated from version 1.3.2 to 1.3.3 again and again. After installing update netbeans wants to restart but it only end itselfes. It dont start up again. Looking for updates (after manual restart) claims again that this module need to be updated. Details of Autoupdate for this module: Netbeans Plugin Development Installed version:1.3.2 Available version:1.3.3 Date: 29.10.09 Source: NetBeans Running System: Product Version: NetBeans IDE 6.7.1 (Build 200907230233) Java: 1.6.0_03; Java HotSpot(TM) Client VM 1.6.0_03-b05 Could be similar to bug 129319 but reloading catalog didn't work. And yes-I imported my prior NB6.5-settings. But its a long time ago and everything worked fine in NB6.7 and NB6.7.1 until ... I guess I installed an update of autoupdater module for NB6.7.1 a few weeks ago (but I can't swear to that).
PetrG, this is about the last module update for 6.7.1 that you published for us, the apisupport module. Dmitry, can this be a bug in autoupdate?
1) Please run the NetBeans from command line (c:\windows\system32\cmd.exe) using <installdir>\bin\netbeans.exe command 2) Increase the buffer of scroll lines (Right-click on the "cmd.exe" window, choose Properties, then "Layout" tab, set 2000 for Height in Screen Buffer Size 3) Update "Netbeans Plugin Development", restart 4) Attach files ~/.netbeans/6.7/var/log/messages.log ~/.netbeans/6.7/var/log/messages.log.1 5) Check the console (cmd.exe) - is there any exception thrown there? Do right-click on cmd.exe window, choose Edit->Select All, press Enter, open Notepad, Ctrl-V, save the resulting file and attach it to this issue. Thanks.
Created attachment 90609 [details] Message.log after (manual) restart on CMD
Created attachment 90611 [details] Message.log.1 after (manual) restart on CMD
Created attachment 90615 [details] CMD-Output after (manual) restart on CMD All files attached as desired. No exceptions occured on cmd. Automatic restart didn't worked by running from cmd neither. But I had to "force" the command prompt to return after exiting netbeans by pressing CTRL-C before I could restart it manually. But why? There was no subsequent process of this cmd-instance (checked it using Sysinternals Process Explorer) Anyway, update is shown again.
Possibly I found the reason. I updated my JDK to Java: 1.6.0_16; Java HotSpot(TM) Client VM 14.2-b01 and the VM crashed while starting Netbeans. At first I restored my netbeans.conf file to original installed version and et'voila the missing updater-splash-screen came up and netbeans started successfully (but of course without using my own projects dir). I restored my modified netbeans.conf and the VM crashes again(so the outstanding update was not the reason of VM-crash). By running it from CMD (thanks for this very usefull hint:O) I got the message "Conflicting collector combinations in option list". Finally I found out that the VM-Switch "-J-XX:+UseConcMarkSweepGC" even without combining it incorrectly with "-J-XX:+UseParallelGC" caused the new VM to crash. Maybe this was also the cause of failing update and only the older VM ignored the error silently. Everything works fine now! No pending updates shown. I think it was a minor fault combination of mine ;O) But thanks a lot for help and your time!
Yes, it looks like the cause of the issue.
Sorry, but problem occured again (pending updates, no automatic restart). Got an update notification for module "IDE Platform" Installed version:1.6.3 Available version:1.6.4 Date: 04.11.09 Source: NetBeans Restoring the VM-Parameters in my netbeans.conf file to original installed version with my own profile directory didn't work. I cleared up the complete var-directory to eliminate any possible "pitfalls" in cache but it didn't help. Reset project dir to an empty one brings the updater-splash-screen to come up and the update is installed - so the update-hook into the startup process is set correctly I think. However I guess there is something in my project dir that makes the current version of auto-update-module to ignore the startup-hooked update-process or something like that. For now I have no pendig updates left to reproduce the error. But next time a get an update notification I'm afraid the problem will return. Is there something I can do to find out why the auto-update-module fails silently? To switch my netbeans.conf to an empty project dir is a not really handy workaround :O(
All the possible issues with update on Windows can be checked adding "--trace c:\out.log" arguments added to the "Target" option in NetBeans desktop shortcut. Please do the update (which doesn`t result into the update, actually), and attach the c:\out.log file to this issue.
Created attachment 92035 [details] trace&Message-Logs for current failing update Attached Logfiles trace.log (caused by "--trace"-Option at netbeans shortcut, made after netbeans post-update-restart button was pressed but netbeans only ended) and all todays message.log-files. Tried to update module "IDE Platform" Installed version:1.6.4 Available version:1.6.5 Date: 27.11.09 Source: NetBeans Homepage: http://www.netbeans.org/
Can`t say for sure but it is probably due to the bug in autoupdate (discussed in Issue 178175 and Issue 175196). Patch is in progress.
patch has been published hopefully this issue is also fixed.