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.
I dowloaded the full distribution for both version 6.0.1 and RC1 for 6.1. I am running JDK Standard edition 1.6_5. Both installers fail at the same place with the same message. An unexpected exception happened in thrwead Thread-20 Exception: java.lang.IllegalArgumentException: "null" expected to be an integer.
Created attachment 60240 [details] Install log file with the error in it.
Hi, Could you please attach the *installation* log file, not the netbeans log file? The installation log file is available at C:\Documents and Settings\soliphant\.nbi\log directory. Could you please attach the file C:\Program Files\NetBeans 6.0.1\nb6.0\servicetag\registration.xml ? From the messages.log I see: java.lang.IllegalArgumentException: "null" expected to be an integer at com.sun.servicetag.Util.getIntValue(Util.java:66) at com.sun.servicetag.Registry.parseServiceTag(Registry.java:460) at com.sun.servicetag.Registry.getServiceTag(Registry.java:424) at org.netbeans.modules.reglib.NbServiceTagSupport.installSystemServiceTag(NbServiceTagSupport.java:639) at org.netbeans.modules.reglib.NbServiceTagSupport.createNbServiceTag(NbServiceTagSupport.java:194) at org.netbeans.modules.registration.NbInstaller.restored(NbInstaller.java:98) at org.netbeans.core.startup.NbInstaller.loadCode(NbInstaller.java:378) [catch] at org.netbeans.core.startup.NbInstaller.load(NbInstaller.java:297) Something wrong with registration...
Created attachment 60284 [details] Install log as requested.
oops. I had already deleted the failed install. I will run the install again and load the registration file from that one. Steve
Looks like the same issue when calling createNbServiceTag from installer... java.lang.IllegalArgumentException: "null" expected to be an integer at org.netbeans.modules.servicetag.Util.getIntValue(Util.java:101) at org.netbeans.modules.servicetag.Registry.parseServiceTag(Registry.java:495) at org.netbeans.modules.servicetag.Registry.getServiceTag(Registry.java:459) at org.netbeans.modules.reglib.NbServiceTagSupport.installSystemServiceTag(NbServiceTagSupport.java:639) at org.netbeans.modules.reglib.NbServiceTagSupport.createNbServiceTag(NbServiceTagSupport.java:194) at org.netbeans.installer.wizard.components.actions.netbeans.NbServiceTagCreateAction.createSTNetBeans(NbServiceTagCreateAction.java:178) at org.netbeans.installer.wizard.components.actions.netbeans.NbServiceTagCreateAction.execute(NbServiceTagCreateAction.java:150) at org.netbeans.installer.wizard.components.WizardAction$1.run(WizardAction.java:120)
Created attachment 60300 [details] registration.xml file for 6.1 RC1
Created attachment 60301 [details] nbi\log for version 6.1 RC1 install failure
Marek, It seems that installSystemServiceTag() is executed thus stcclient is presented on the system (windows), right? has this scenario been already tested? CC-ing Marian.
Just in case we have two separate issues, I am going to download version 6.0.1 and re-install that one.
Created attachment 60304 [details] Screen prints that show where the install starts and where it hangs.
In answer to your question, stcclient is the task that is running and appears to be hung.
I just realized something that could be causing a problem. I have Tumbleweed installed already for another application. Could this be causing a conflict of some sort?
Hi, As far as I understand, Tumbleweed has STClient.exe installed (probably) at C:\Program Files\Tumbleweed\STClient\STClient.exe Sun`s client is usualy installed at C:\Program Files\Sun\servicetag\stclient.exe The stclient.exe (whatever installed) is also "registered" it at HKLM\software\microsoft\windows\currentversion\app paths\stclient.exe on the first execution (if I am not mistaken) The JDK`s ServiceTag implementation reads this registry key (Util.getWindowsStClientFile()) and uses Tumbleweed`s stclient for the servicetag purposes. That is likely wrong...
We did not have stclient for Windows. Where did you get it? I will try to reproduce it. Simply stclient returns unexpected output. You also said that you have installer hang. I do not know if it is the same problem or not. Please could you attach thread dump of installer JVM when installer hangs?
If Dmitry is right it is *bad* conflict. I do not know how to detect it. I will pass this to JDK. In current code we have our own private copy of com.sun.servicetag so we will try to handle this in our code. Dmitry: Log from installer when it calls reglib is NOT sufficient. Please is there any way how to print call stack of eventual exception thrown from reglib?
The stclient is installed as part of my full Tumbleweed FTP client install. I have this application installed for some technnical support for another project. Can you tell me where the thread dump is kept and I will upload it.
Where to get Tumbleweed? On Google this word is quite common. No idea what search result is relevant. Thanks. Lowering priority to P3 as this happens only to unfortunates using Tumbleweed which is not very common hopefully. Anyway we will try to fix it soon.
> Dmitry: Log from installer when it calls reglib is NOT sufficient. What is the sufficient log then? > Please is there any way how to print call stack of eventual exception thrown from reglib? Is the following stack now full ? Actually it is the almost the same as in messsages.log. java.lang.IllegalArgumentException: "null" expected to be an integer at org.netbeans.modules.servicetag.Util.getIntValue(Util.java:101) at org.netbeans.modules.servicetag.Registry.parseServiceTag(Registry.java:495) at org.netbeans.modules.servicetag.Registry.getServiceTag(Registry.java:459) at org.netbeans.modules.reglib.NbServiceTagSupport.installSystemServiceTag(NbServiceTagSupport.java:639) at org.netbeans.modules.reglib.NbServiceTagSupport.createNbServiceTag(NbServiceTagSupport.java:194) .... Anyway the same exception is thrown in the netbeans messages log file so, I guess, you know the way how to handle it in the way you like.
How to get thread dump: First you must get PID of JVM process. Use jps (it is utility from JDK located in bin directory). Once you have PID you can use jstack <PID> to log thread dump to console. You can redirect it to file: jstack <PID> > threaddump.txt. Eg. if you find installer has PID 2135 you will use: jstack 2135 > threaddump.txt and attach generated file to issue.
1, what has been tested with registration? -> http://wiki.netbeans.org/TS_61_UserRegistration A Tumbleweed scenario hasn't been covered (and probably won't for future however we will see) 2, How to generate thread dump? -> http://wiki.netbeans.org/GenerateThreadDump
I will try to get time today for a thread dump. I may not get to it until the weekend, however. In any case, it looks to me that the solution, for now, is to install NetBeans somewhere else or remove Tumbelweed from my machine.
Yes Dmitry is right. What is value below HKEY_LOCAL_MACHINE\software\microsoft\windows\currentversion\app paths\stclient.exe? If it points to different exe than Sun's stclient.exe then it is wrong.
The values under HKEY_LOCAL_MACHINE\software\microsoft\windows\currentversion\app paths\stclient.exe are: Key: (Default) C:\Program Files\Tumbleweed\STClient\stclient.exe Key: DESTDIR C:\Program Files\Tumbleweed\STClient I imagine that if I change that, then NetBeans will work and Tumbleweed will not.
Yes. It is reason why it fails. You can use command line option -J-Dnb.registration.enabled=false to disable registration module. This way exception will not happen. It is workaround. I passed this problem to JDK.
I added the command line argument you suggested and the IDE comes up. It also has the message "Cannot connect to internet" in three different places. Is that due to the stclient issue or would this be due to our Websense application?
This should not break anything else. Are there any details in IDE log? (messages.log file in user dir)
I get the following message several times. I expect it is websense doing this. Other applications will pop up a user ID password box to send back to websense so that the connection can go through for that application. java.io.IOException: java.io.IOException: Server returned HTTP response code: 401 for URL: http://10.10.1.125:15871/cgi-bin/authenticate.cgi?ws-session=3592152686 at org.netbeans.modules.autoupdate.updateprovider.AutoupdateCatalogCache.notifyException (AutoupdateCatalogCache.java:183) at org.netbeans.modules.autoupdate.updateprovider.AutoupdateCatalogCache.copy(AutoupdateCatalogCache.java:178) at org.netbeans.modules.autoupdate.updateprovider.AutoupdateCatalogCache.writeCatalogToCache (AutoupdateCatalogCache.java:103) at org.netbeans.modules.autoupdate.updateprovider.AutoupdateCatalogProvider.refresh (AutoupdateCatalogProvider.java:121) at org.netbeans.modules.autoupdate.services.UpdateUnitProviderImpl.refresh(UpdateUnitProviderImpl.java:162) at org.netbeans.api.autoupdate.UpdateUnitProvider.refresh(UpdateUnitProvider.java:158) [catch] at org.netbeans.modules.autoupdate.ui.actions.AutoupdateCheckScheduler$3.run(AutoupdateCheckScheduler.java:127) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:561) at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:986)
You should configure your security software to allow IDE connect to Update Center. It has nothing to do with registration. Though if registration is enabled it also can check registration status on IDE start to confirm product registration status.
This is handled by JDK as issue #6696399. I will leave this issue open. I will port fix into our code.
*** Issue 143787 has been marked as a duplicate of this issue. ***
Fixed as issue #150198. Search for stclient.exe is now more specific - also path is checked to make sure it is stclient.exe from service tag infrastructure. *** This issue has been marked as a duplicate of 150198 ***