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.
Product Version = NetBeans IDE Dev (Build 201003220200) Operating System = Linux version 2.6.32-trunk-686 running on i386 Java; VM; Vendor = 1.6.0_18 Runtime = Java HotSpot(TM) Client VM 16.0-b13 I have an existing Glassfish V3 instance running on my computer which was installed with NetBeans 6.8. Now under 6.9, each time I try to create a Ruby on Rails application, the IDE prompts me for my admin login credentials for the Glassfish server I have on port 4848 (from NB 6.8). This is prior to the activation of the JavaEE capabilities within the 6.9 IDE.
Created attachment 95626 [details] IDE Log File
Did you import settings from 6.8? Could you trigger a thread dump while the authentication dialog is open and attach it to this issue? Where are the various bits installed... path to 6.8 install, path to gf install for 6.8, path to 6.9 install, path to gf install for 6.9.
I'm working on the thread dump right now, but here are the particulars: NetBeans 6.8: Installed as root user for global access to /usr/share/NetBeans-6.8 with symlink to /usr/bin/netbeans NetBeans 6.9: Installed as myself to ~/Apps/netbeans-dev-201003230200 Glassfish from NetBeans 6.8: Installed as root user for global access to /usr/share/glassfishv3 and configured as a service to be launched during boot. Currently hosts an instance of Liferay Portal. Glassfish from NetBeans 6.9: Installed as myself to ~/Apps/sges-v3 just as it would be for any dev installation.
Created attachment 95720 [details] Thread dump for IDE. This is the thread dump for a clean install of 20100323xxxx
It looks like the two instances are confusing NB... At some point, NB is asking the plugin... hey is this server running (by host and port)... the plugin tries to find out by pinging that port. Since you have the server hosting liferay on the same set of ports as the server you are using for development, the IDE will try to ping that running server to find out if the server @ host/port is the server that we want to work with... The easiest work-around: in 6.9... remove the GF server node from the Services explorer and then add a new instance back... but create a personal domain (do not register domain1). the personal domain will end up on custom ports that will not overlap with the liferay server.
In previous versions of the installer, when the glassfish server was installed, the installer was smart enough to configure the ports for it based on user input. I would suggest that the proper behavior is for the installer to do the check on the glassfish instance using the admin port during installation and not later on, after the installer has installed competing software. I would also recommend, since the development instance may be a significantly different version than the running version) that the installer, if it determines that the server is installed, prompt the user for ports on which to install the development instance. Then, armed with this information, the installer will configure the development instance to run on the user provided ports.
esmithbss: which installer are you talking about in http://netbeans.org/bugzilla/show_bug.cgi?id=182613#c6?
In the installers for NetBeans when it included Glassfish V2, there were additional fields in the Glassfish installation that allowed you to specify the administrator name/password, the port for the server and the admin port for the server.
that feature would need to be added to the installer.
Assigned to new owner.