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 138677 - view update center problems
Summary: view update center problems
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 6.x
Hardware: Sun Windows XP
: P3 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-01 06:58 UTC by dpkumar
Modified: 2008-09-12 01:10 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dpkumar 2008-07-01 06:58:33 UTC
NB Build:NetBeans IDE Build 200806300002
JDK:jdk1.6.0_06

Steps to reproduce:
1.Install NB IDE
2.Right click on the server node, select GFV3TP2
2.Set path as install_Dir:GlassFish_V3_TP2 and start download.(In my case I set path as e:GlassFish_V3_TP2, click finish
after downloading.
3.Now right click on the GlassFish V3TP2 server select " View Update Center".

On selecting View Update center getting exception:

java.io.IOException: The pipe is being closed
	at java.io.FileOutputStream.writeBytes(Native Method)
	at java.io.FileOutputStream.write(FileOutputStream.java:260)
	at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
	at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
	at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:278)
	at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:122)
	at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:212)
	at org.netbeans.modules.glassfish.common.actions.ViewUpdateCenterAction.isUCInstalled(ViewUpdateCenterAction.java:173)
	at org.netbeans.modules.glassfish.common.actions.ViewUpdateCenterAction.access$000(ViewUpdateCenterAction.java:69)
	at org.netbeans.modules.glassfish.common.actions.ViewUpdateCenterAction$1.run(ViewUpdateCenterAction.java:109)
	at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:561)
[catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:986)

NOTE: 

This happens at very first time of downloading GlassFish V3TP2 with wrong path. When you select "View Update Center
second time it will say "The system cannot find the path specified". 
Remaining all the server instances are working fine.
Comment 1 _ pcw 2008-07-04 01:01:32 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.)
Comment 2 dpkumar 2008-07-04 07:02:58 UTC
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.


Comment 3 _ pcw 2008-07-04 20:15:37 UTC
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.
Comment 4 _ pcw 2008-07-21 03:55:43 UTC
Not surprisingly, sanity checking whether or not update center is installed is pretty braindead.  I'll make it more robust.
Comment 5 Vince Kraemer 2008-07-24 02:19:24 UTC
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
Comment 6 Vince Kraemer 2008-08-14 21:18:29 UTC
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.
Comment 7 Vince Kraemer 2008-08-15 18:44:36 UTC
http://hg.netbeans.org/main/rev/1394c24aab73

starts to address this... but now I see a core dump when the updatetool starts.

Investigating.
Comment 8 Vince Kraemer 2008-08-15 18:50:59 UTC
filed https://glassfish.dev.java.net/issues/show_bug.cgi?id=5514 to track the issue on the GF side.
Comment 9 Vince Kraemer 2008-09-12 01:10:19 UTC
the issue that I ran into was a patch problem on solaris... see the GF issue for info about the patches required.