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 37010 - Updater hangs when installing Arrow NBMs
Summary: Updater hangs when installing Arrow NBMs
Alias: None
Product: platform
Classification: Unclassified
Component: Autoupdate (show other bugs)
Version: -S1S-
Hardware: PC Windows ME/2000
: P2 blocker (vote)
Assignee: Petr Hrebejk
Depends on: 37133
  Show dependency tree
Reported: 2003-11-04 12:55 UTC by L Martinek
Modified: 2003-12-22 08:11 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

exception and thread dump (5.08 KB, text/plain)
2003-11-04 12:56 UTC, L Martinek
exception and thread dump from my colleague (4.10 KB, text/plain)
2003-11-04 12:57 UTC, L Martinek
exception and thread dump (4.91 KB, text/plain)
2003-11-04 16:17 UTC, Jaromir Uhrik

Note You need to log in before you can comment on or make changes to this bug.
Description L Martinek 2003-11-04 12:55:27 UTC
[S1S5 Nevada FCS, JDK 1.4.2_02]

I installed manually downloaded NBMs for Arrow.
Exception from updater was thrown after restart
and updater hanged. If I tried to install NBMs for
the second time, it worked. It happened to my
colleague too.
Comment 1 L Martinek 2003-11-04 12:56:50 UTC
Created attachment 12055 [details]
exception and thread dump
Comment 2 L Martinek 2003-11-04 12:57:29 UTC
Created attachment 12056 [details]
exception and thread dump from my colleague
Comment 3 Petr Hrebejk 2003-11-04 13:00:59 UTC
Please specify what .nbms you installed and where you got them.
Comment 4 Jaromir Uhrik 2003-11-04 16:16:13 UTC
When I have no Corba module installed before installing NBMs then the 
dump is similar to that with id=12056. Now I installed the Corba 
module from the UC server first and then installed NBMs. Here is the 
thread dump:
Comment 5 Jaromir Uhrik 2003-11-04 16:17:38 UTC
Created attachment 12061 [details]
exception and thread dump
Comment 6 Jaromir Uhrik 2003-11-05 09:15:00 UTC
I tried to install/update all modules from the ftportal and the 
dump is similar to that with id=12056.
Comment 7 Antonin Nebuzelsky 2003-11-05 15:12:16 UTC
I tried reproducing this bug with different subsets of NBMs. I did not
encounter the problem always. The problem did NOT appear for example

* if I installed only the corba.nbm
* if I installed everything except corba.nbm
* if I installed everything except autoupdate.nbm

The problem DID appear

* if I was installing corba.nbm with autoupdate.nbm at once, just
these two modules were enough for the problem to appear

Both autoupdate.nbm and corba.nbm have the "global" flag. They both
install something under INSTALLDIR/lib.

Perhaps this is the key to the problem.
Comment 8 rnovak 2003-11-06 14:18:46 UTC
I've done some investigation and I found out, that the problem is most
probably caused by update of the autoupdate module. The problem
appears when autoupdate module is being updated together with some
other modules. The reasons:
* I wasn't able to reproduce the problem, when I tried to install any
other set of modules except of autoupdate module

* when I reproduced the problem, progress bar always stoped when the
updater was processing module autoupdate, doesn't matter what
exception is thrown. Updater fails on module following after
autoupdate module.

* there is no problem to install autoupdate module only

* info.xml files are correct for all NBMs

As far as I know, there is a fix in updater.jar and I suspect, that
this fix causes reported problem.
Comment 9 Petr Hrebejk 2003-11-06 14:26:32 UTC
Updating updater .jar is not and will not be supported feature of the
AU module
Comment 10 Antonin Nebuzelsky 2003-11-07 12:44:17 UTC
:-)) It always worked, we delivered fixes to updater.jar in previous
releases, without any problems.

Were there any changes in Updater for NB3.5 / S1S5 which could cause
this problem?
Comment 11 Antonin Nebuzelsky 2003-11-07 13:56:05 UTC
For the time being I suggest that autoupdate.nbm is excluded from the
Nevada Patch 1. The one fix which is in autoupdate.nbm is not critical

With regard to either removing the fix #34355 from Arrow or leaving it
there, I think we can keep it there. I believe this fix is not the
cause of this problem. I believe this problem is in the updater code
already in FCS version and shows up if updater.jar is being replaced
by a new version.

However, this problem needs to be resolved because it prevents us from
updating autoupdate module, and it might become a critical issue if a
fix for autoupdate module must be delivered to users.

Comment 12 Petr Hrebejk 2003-11-10 10:48:46 UTC
Updating autoupdate module is OK. Up[dating the updater.jar is not.
Maybe it worked by accident but it never was feature of the AU to
update the updater.jar. and as said before will not be.
Comment 13 Antonin Nebuzelsky 2003-11-10 11:03:07 UTC
OK then, see the new bug #37119, which must be resolved:

And I think Support and QA would like to comment on this suggested
impossibility of patching updater.jar! Karthik, please, raise a new P1
about updating updater.jar if you think appropriate.
Comment 14 Unknown 2003-11-10 23:40:35 UTC
I have created a new bug to track the
issue of the inability to update updater.jar
Comment 15 Unknown 2003-12-21 21:10:15 UTC
The updater hangs only when updater.jar (included in autoupdate.nbm)
itself is updated. Since that issue is handled by #37133,, this issue can
be closed.
Comment 16 Lukas Hasik 2003-12-22 08:11:43 UTC