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.
Summary: | view update center problems | ||
---|---|---|---|
Product: | serverplugins | Reporter: | dpkumar <dpkumar> |
Component: | GlassFish | Assignee: | Vince Kraemer <vkraemer> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | issues |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | Sun | ||
OS: | Windows XP | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
dpkumar
2008-07-01 06:58:33 UTC
Can you run update center from the command line? Does it run the installer or run the actual app (whose installation at this point appears to be messed up.) I ran update tool from the command line, it ran successfully with the following message F:\GlassFish_V3_TP2\bin>updatetool.bat The software needed for this command (updatetool.bat) is not installed. Press any key to install the necessary software, or Ctrl-C to quit. After software installation is completed you may re-run this command. Press any key to continue . . . Platform: windows-i386 Software repository: http://pkg.glassfish.org/dev/windows/gf3000_2000/ Installing pkg packages... Installing: python2.4-minimal@2.4.4,0-8.724:20080612T134356Z python2.4-minimal@2.4.4,0-8.724:20080612T134356Z: manifest file doesn't exist ye t, fetching from server...... ............ ................. updatetool@2.0,0-8.837:20080629T113140Z: installing files... Update Center initialization complete. Thanks. It looks like update center installation failed due to network failure but afterwards, the IDE was failed to detect that it will still not installed. The second invocation after the first installation failure should have tried to install it again. I'll look at the code and see if I can find the flaw by inspection. Not surprisingly, sanity checking whether or not update center is installed is pretty braindead. I'll make it more robust. I could not replicate the 'exact' situation. I did notice that if I put the install at c:foobarloo (note the missing slash...) that the update center installer window had the text: The system cannot find the path specified. The server was able to start and stop correctly. the admin gui was ok... Here is a snippet out of the Glassfish/Instances/.nbattrs file <fileobject name="instance_2"> <attr name="adminPort" stringvalue="4848"/> <attr name="debugPort" stringvalue="8787"/> <attr name="displayName" stringvalue="GlassFish V3 TP2"/> <attr name="domainname" stringvalue="domain1"/> <attr name="domainsfolder" stringvalue="C:\sun\NetBeansDev200807221016\foobarloo\glassfish\domains"/> <attr name="homefolder" stringvalue="C:\sun\NetBeansDev200807221016\foobarloo\glassfish"/> <attr name="host" stringvalue="localhost"/> <attr name="httpportnumber" stringvalue="8080"/> <attr name="installfolder" stringvalue="C:foobarloo"/> <attr name="jvmMode" stringvalue="normalMode"/> <attr name="password" stringvalue="adminadmin"/> <attr name="url" stringvalue="[C:\sun\NetBeansDev200807221016\foobarloo\glassfish] deployer:gfv3:localhost:8080"/> <attr name="username" stringvalue="admin"/> </fileobject> it looks like installfolder is incorrect. I think this is a p3... the user has to delete a valid file spec and input a "tricky" one to trigger this issue... Since this is a registration wizard issue... I am going to reassign it to vkraemer It looks like we need to ask for the v3 bits to come from download.java.net/glassfish/v3/promoted... I dropped build 18 over the 15b bits and could not reproduce this issue. http://hg.netbeans.org/main/rev/1394c24aab73 starts to address this... but now I see a core dump when the updatetool starts. Investigating. filed https://glassfish.dev.java.net/issues/show_bug.cgi?id=5514 to track the issue on the GF side. the issue that I ran into was a patch problem on solaris... see the GF issue for info about the patches required. |