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 256164 - 20151025 local field "detail" get's set to null in progress object
Summary: 20151025 local field "detail" get's set to null in progress object
Status: NEW
Alias: None
Product: installer
Classification: Unclassified
Component: Code (show other bugs)
Version: 8.1
Hardware: PC All
: P3 normal (vote)
Assignee: Libor Fischmeistr
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-25 10:01 UTC by Chiana
Modified: 2015-10-26 14:00 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Installation log (1.66 MB, application/octet-stream)
2015-10-25 10:02 UTC, Chiana
Details
Installation log (1.66 MB, application/octet-stream)
2015-10-25 10:17 UTC, Chiana
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Chiana 2015-10-25 10:01:30 UTC
[ BUILD # : 201510250002 ]
[ JDK VERSION : 1.8.0_45 ]

New IDE failed to install.
Comment 1 Chiana 2015-10-25 10:02:15 UTC
Created attachment 156964 [details]
Installation log
Comment 2 Chiana 2015-10-25 10:04:42 UTC
Looks like a lot of NPE's in the log.
Comment 3 Chiana 2015-10-25 10:17:12 UTC
Created attachment 156965 [details]
Installation log

Second attempt this time without uncheking the Apache server as I don't want that one installed.
Comment 4 Chiana 2015-10-25 11:29:41 UTC
I've looked at this, and it seems somewhere there is a call to Progress.setDetail with a null value, this means that this.detail get's set to null and the NEXT call will fail as the check is "this.detail.equals" without checking that "this.detail" is not null.
The simplest fix is imho to add the lines;
"  if (this.detail == null) {
      this.detail=StringUtils.EMPTY_STRING;
   }"
as the first lines in Progress.setDetail.
There are a few other ways too.
Comment 5 Chiana 2015-10-25 11:34:08 UTC
The cause of the above seems to be a missing bundle, excerpt from the log;
[2015-10-25 11:13:14.909]:         Can`t load message in bundle org.netbeans.installer.product.components.Bundle for key NCCL.install.netbeans.clusters using [sun.misc.Launcher$AppClassLoader@1497b7b1] classloader
[2015-10-25 11:13:14.909]:         java.lang.NullPointerException
[2015-10-25 11:13:14.909]:         	at org.netbeans.installer.utils.progress.Progress.setDetail(Progress.java:209)
[2015-10-25 11:13:14.909]:         	at org.netbeans.installer.utils.progress.Progress$1.progressUpdated(Progress.java:349)
[2015-10-25 11:13:14.909]:         	at org.netbeans.installer.utils.progress.Progress.notifyListeners(Progress.java:478)
[2015-10-25 11:13:14.909]:         	at org.netbeans.installer.utils.progress.CompositeProgress.progressUpdated(CompositeProgress.java:299)
[2015-10-25 11:13:14.909]:         	at org.netbeans.installer.utils.progress.Progress.notifyListeners(Progress.java:478)
[2015-10-25 11:13:14.909]:         	at org.netbeans.installer.utils.progress.Progress.setDetail(Progress.java:212)
[2015-10-25 11:13:14.909]:         	at org.netbeans.installer.product.components.NbClusterConfigurationLogic.install(NbClusterConfigurationLogic.java:134)
[2015-10-25 11:13:14.909]:         	at org.netbeans.installer.product.components.Product.install(Product.java:358)
[2015-10-25 11:13:14.909]:         	at org.netbeans.installer.wizard.components.actions.InstallAction.execute(InstallAction.java:155)
[2015-10-25 11:13:14.909]:         	at org.netbeans.installer.wizard.components.WizardAction$1.run(WizardAction.java:123)
[2015-10-25 11:13:14.909]:         NameResolver - to parse Unknown Error
Comment 6 Chiana 2015-10-26 10:59:15 UTC
A better description
Comment 7 Antonin Nebuzelsky 2015-10-26 11:21:32 UTC
I see "Insufficient disk space for extracting the installation data".

Can that be the cause?
Comment 8 Chiana 2015-10-26 12:05:31 UTC
(In reply to Antonin Nebuzelsky from comment #7)
> I see "Insufficient disk space for extracting the installation data".
> 
> Can that be the cause?

Probable not as the drive in question has about 800 Gig of free space.
Comment 9 Chiana 2015-10-26 14:00:53 UTC
I've been thinking, now, I don't know where that diskspace message originates from so i haven't checked for this, could this be caused by the fact that there are too much diskspace free? I mean, the check itself get's confused because of an overflow making the diskspace look negative (or simply needs an alternate way to check for free space)?