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.
Netbeans build 200708081200, Glassfish SDK build java_app_platform_sdk-5_03-fcs-bin-b25-windows-08_aug_2007, JDK1.6.0_02 Win Vista When I add this Glassfish into Runtime tab and start it,I can't see AM under its node. In latest SDK build I've everything works and also when I run update tool or compare builds visually,everything looks like this is version of Glassfish with Identity (and AM) already installed. I think there could have been some recent changes in Glassfish builds(maybe config files),which are causing that IDE don't detect AM in the Glassfish. MEMO: Older SDK build I used for comparison is from 19.7.2007 . You can download latest SDK build from http://javaweb.sfbay/java/re/javaeesdk/5.0_03/nightly/bundles/latest/ .
I noticed that the identity stuff wasn't installed in the server when I was working on another issue using b58... This node comes from the identity module team... Reassigning to them for further investigation.
Just tried it with the latest NB build and eesdk b26 and I can see the Access Manager node under the appserver node.
I reproduced it on Vista with b27.Seem to be bug in installer - AM is checked and installed,but when I start server,I'm not able to access amserver console,because amserver isn't deployed. If I deploy amserver manually (copy amserver.war into autodeploy folder),I can access amserver through web browser,but it's still invisible for Netbeans,because if I then add this SDK glassfish in Runtime tab (I mean the same glassfish I just deployed amserver.war and checked console),there's still no AM node.I think this bug is restricted only to Vista,since I'm not able to reproduce it on any other system.
Please file a bug against access manager. I don't know how import Vista is to access manager, so expect this to be a low priority bug for them. We will adjust our bug priority according the priority on the corresponding bug on the access manager.
I've filled this issue in Bugster as http://bt2ws.central.sun.com/CrPrint?id=6595833 and set sterting priority to P2.
Since this issue is restricted to Windows Vista which still has a relatively small userbase compared to XP, and this is a bug on the Access Manager installer, we will apply for beta1 waiver.
I agree with beta1 waiver. I must mention however,that I've reproduced issue also on Ubuntu on computer using DHCP network connection(not fixed IP address). SDK glassfish was unable to start,since it cannot connect,when my computer name was other than "localhost".I've changed it and then SDK started,but it behaved in IDE same way as described in this issue. I had to reinstall SDK glassfish with localhost computer name set and then everything worked. I think this workaround could be also working with Vistas,but I haven't checked it yet,but it could be useful,if I could find somebody to check SDK on Vistas with fixed IP address,because it seems to me,that SDK glassfish during its installation obtains and hardcodes somewhere IP address of computer and when it changes,it's unable to work properly. I will update Bugster issue with these new information. If I'll found,that DHCP is main cause of the problem,I'll lower the issue priority,because this is not typical scenario for great majority users,as we encountered in previous releases.
So the workaround with renaming computer to "localhost" works also on Vista and this is definitely DHCP problem. Decreasing priority to P3.
According to mail from SDK installer team I checked last beta installer and it successfully installs on non-localhost computer,so the problem is fixed.I'll close bugster issue and then this one.
My previous success was caused by accidentally disconnected network cable. The issue is still ON and I've already informed responsible team. Disconnecting of network cable during install of SDK glassfish seems to be another workaround.
The issue has been fixed and closed in Bugster. Issue remains only for computer's,where previous builds of SDK was installed,but it's related to SDK uninstaller now and common user don't see it. Confirmed on couple of clean computers. Closing as fixed.
v.