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.

Bug 235296 - When plugins marked restart required are updated one can start two netbeans at once and it breaks the update
Summary: When plugins marked restart required are updated one can start two netbeans a...
Status: NEW
Alias: None
Product: platform
Classification: Unclassified
Component: Autoupdate (show other bugs)
Version: 7.3
Hardware: PC Windows 7
: P4 normal with 1 vote (vote)
Assignee: Libor Fischmeistr
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-30 09:07 UTC by natit
Modified: 2014-02-10 14:15 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
packed log folder with screenshot of taskmanger (465.77 KB, application/octet-stream)
2013-09-02 10:00 UTC, natit 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description natit 2013-08-30 09:07:49 UTC 
We are using the Netbeans platform for our ERP system. We push updates about every 1 - 2 months to our users. We have over the last year experienced about 1%% of our users installation stops working each update. 


Stops working is defined as: Netbeans starts up, the topcomponent is blank and the title says Netbeans [internal build number] or somthing similar. Sometimes some third party libs that require licences pop up with a warning that the license is missing (which we supply in our primary module installer).


To reproduce update a plugin that requires restart, after pressing finish for restart quickly also doubleclick the application icon (you have maybe 1-2 seconds probably dependent on hardware and how big the plugins are(?)).


Here is a link to our default updates.xml that causes the bug. I was also once able to cause an infite loop where the application would just restart when you quit it. Only way to exit our app then was to manually kill the app "unpack200.exe" (which kept respawining about once each second)


http://lisens.zirius.no/ZiriusNetbeansUpdateCenter/31/nightly/updates.xml


We have had this bug in our releases since we started using Netbeans platform in 7.0, but never understood what was happening. We where finally able to reproduce it ourselfs now.


It is a pretty strange bug, sometimes starting twice doesn't matter, the program seems to work fine after, other times it does not, which makes it a bit difficult to reproduce.


To make an broken application work again one has to reinstall the app, or sometimes just change userdir (or delete the old one).
Comment 1 Jiri Rechtacek 2013-08-30 11:19:20 UTC 
What release of RCP platform are you using? Could you send also a messages.log and updater.*.log when the bug appeared? Thanks
Comment 2 natit 2013-09-02 10:00:12 UTC 
Created attachment 139571 [details]
packed log folder with screenshot of taskmanger

Attached is a screenshot from the processes in windows task manager

messages.log.*
and 
updater.log.*


I cleaned the user dir (deleted it) before starting and updating, then i pressed enter on my shortcut icon while the updater was starting and patching more than a few times



The netbeans current platform is 7.3 build 201302132200 but we have as i mentioned had this bug since we started with netbeans at 7.0


To stop the infinite spawn of our application i had to run the following commands in quick succession


C:\Users\Petter>taskkill /f /im unpack200.exe*
SUCCESS: The process "unpack200.exe" with PID 4868 has been terminated.
SUCCESS: The process "unpack200.exe" with PID 10208 has been terminated.
SUCCESS: The process "unpack200.exe" with PID 10820 has been terminated.
SUCCESS: The process "unpack200.exe" with PID 10980 has been terminated.
ERROR: The process "unpack200.exe" with PID 11748 could not be terminated.
Reason: There is no running instance of the task.

C:\Users\Petter>taskkill /f /im ziriuserp31.exe*
SUCCESS: The process "ziriuserp31.exe" with PID 7196 has been terminated.
SUCCESS: The process "ziriuserp31.exe" with PID 10396 has been terminated.
SUCCESS: The process "ziriuserp31.exe" with PID 892 has been terminated.
SUCCESS: The process "ziriuserp31.exe" with PID 8576 has been terminated.
SUCCESS: The process "ziriuserp31.exe" with PID 12228 has been terminated.
SUCCESS: The process "ziriuserp31.exe" with PID 9888 has been terminated.
SUCCESS: The process "ziriuserp31.exe" with PID 6580 has been terminated.
SUCCESS: The process "ziriuserp31.exe" with PID 10860 has been terminated.
Comment 3 natit 2013-09-13 09:39:46 UTC 
Any news on this? Do you need any more information?
Comment 4 Jiri Rechtacek 2013-11-12 08:17:02 UTC 
(In reply to natit from comment #2)
> I cleaned the user dir (deleted it) before starting and updating, then i
> pressed enter on my shortcut icon while the updater was starting and
> patching more than a few times

This is the important point, starting the application during install(unpacking phase) the updates. I'm sorry I don't plan fix in the near future, patches are welcome.
Comment 5 natit 2013-11-12 08:19:59 UTC 
Hi,

The bug occurs without cleaning the user dir aswell, i just did that to ensure there was nothing wrong with the data in it. (In reply to Jiri Rechtacek from comment #4)

> (In reply to natit from comment #2)
> > I cleaned the user dir (deleted it) before starting and updating, then i
> > pressed enter on my shortcut icon while the updater was starting and
> > patching more than a few times
> 
> This is the important point, starting the application during
> install(unpacking phase) the updates. I'm sorry I don't plan fix in the near
> future, patches are welcome.