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.
With the latest NetBeans Gavotte build, I can add local GlassFish 9.1 (b24), clustered or non-clusterd, successfully. However, when I tried to add a remote GlassFish 9.1 b24 (clustered), I got the attached error message. The remote server instance was running when I registered the instance. My user name and password were correct.
Created attachment 35940 [details] Error dialog when adding remote server instance
I need to make some correction. Last time, I thought I had a local clustered version of GlassFish 9.1 added into NetBeans successfully, but it turns out that the server instance I added was still a regular one. I did run "ant -f setup-cluster.xml" as instructed to set up a clustered instance, but somehow a regular one was created instead. Gopalan suspected that it might have something to do with my glassfish installation directory name containing whitespaces (C:\Documents and Settings\...\GlassFish\). This time, I used GlassFish 9.1 b25 and installed it into a directory that doesn't contain whitespace in the directory name. I had some problem running "asant setup-one-machine-cluster" which seems to hang at the end. I killed it after about 20 minutes. The node agent seemed to be running, as seen below. I could connect to the server through the web admin console. However, when I tried to add the local clustered instance into NetBeans (the latest NetBeans Gavotte build), I got the attached authentication failure, which is different from the one I reported last time on the remote clustered instance. C:\Glassfish-V2-b25\glassfish>ant -f setup-cluster.xml Buildfile: setup-cluster.xml all: get.java.home: setup.init: check-java: get.java.home: setup.init: validate-java: [echo] Current Java Version 1.5.0_08 get.java.home: setup.init: glassfish-jarunpack: get.java.home: setup.init: do.copy.windows: do.copy.unix: do.copy: get.java.home: setup.init: do.token.windows: do.token.unix: do.token: get.java.home: setup.init: do.chmod.unix: do.chmod.linux: do.chmod: get.java.home: setup.init: set.env.win: set.env.unix: set.env: create.domain: [exec] Using default port 3820 for IIOP_SSL. [exec] Using default port 3920 for IIOP_MUTUALAUTH. [exec] Using default port 8686 for JMX_ADMIN. [exec] Domain domain1 created. [exec] WARNING: Existing user preference file .asadminprefs has been detected in your home directory. Application Server administration commands will attempt to use admin user name and password stored in this file and this may cause unexpected behavior and security issues. It is recommended that you delete this file prior to using this new domain, domain1. [exec] Admin login information for host [localhost] and port [4848] is being overwritten with credentials provided. This is because the --savelogin option was used during create-domain command. [exec] Login information relevant to admin user name [admin] for this domain [domain1] stored at [C:\Documents and Settings\jqian\.asadminpass] successfully. [exec] Make sure that this file remains protected. Information stored in this file will be used by asadmin commands to manage this domain. [delete] Deleting: C:\Glassfish-V2-b25\glassfish\passfile BUILD SUCCESSFUL Total time: 21 seconds C:\Glassfish-V2-b25\glassfish>bin\asadmin start-domain domain1 Starting Domain domain1, please wait. Log redirected to C:\Glassfish-V2-b25\glassfish\domains\domain1\logs\server.log. Domain domain1 started. Domain [domain1] is running [Sun Java System Application Server Enterprise Edition 9.1 (build b25)] with its configuration and logs at: [C:\Glassfish-V2-b25\glassfish\domains]. Admin Console is available at [https://localhost:4848]. Use the same port [4848] for "asadmin" commands. User web applications are available at these URLs: [http://localhost:8080 https://localhost:8181 ]. Following web-contexts are available: [/web1 /asadmin ]. Standard JMX Clients (like JConsole) can connect to JMXServiceURL: [service:jmx:rmi:///jndi/rmi://JQIAN-D600XP:8686/jmxrmi] for domain management purposes. Domain listens on at least following ports for connections: [8080 8181 4848 3700 3820 3920 8686 ]. C:\Glassfish-V2-b25\glassfish>cd samples/quickstart/clusterjsp C:\Glassfish-V2-b25\glassfish\samples\quickstart\clusterjsp>..\..\..\bin\asant setup-one-machine-cluster Buildfile: build.xml build_cpath: init_common: envhost: readhost: sethost: envport: readport: setport: envuser: readuser: setuser: envpassword: readpassword: setpassword: envinstance: readinstance: setinstance: update_env: setup_env: checkPlatform: configUnix: configWindows: [echo] on windows init: create_cluster: [echo] Creating cluster cluster1 [exec] Command create-cluster executed successfully. create_nodeagent: build_cpath: init_common: envmasterpassword: readmasterpassword: setmasterpassword: [echo] Creating the node agent cluster1-nodeagent [exec] Command create-node-agent executed successfully. start_nodeagent: build_cpath: init_common: envmasterpassword: readmasterpassword: setmasterpassword: [echo] Start the node agent cluster1-nodeagent [exec] Command start-node-agent executed successfully. Terminate batch job (Y/N)? ^C C:\Glassfish-V2-b25\glassfish\samples\quickstart\clusterjsp> C:\Glassfish-V2-b25\glassfish\samples\quickstart\clusterjsp> C:\Glassfish-V2-b25\glassfish\samples\quickstart\clusterjsp> C:\Glassfish-V2-b25\glassfish\samples\quickstart\clusterjsp>cd ../../.. C:\Glassfish-V2-b25\glassfish>.\bin\asadmin start-node-agent cluster1-nodeagent Could not start the Node Agent cluster1-nodeagent. Node Agent is running. CLI137 Command start-node-agent failed. C:\Glassfish-V2-b25\glassfish>
Created attachment 36032 [details] Problem adding local clustered GlassFish 9.1 b25
I am running a build of release551 with the patch attached to issue 87380. I was able to register a remote clustered domain. My IDE was on a Linux box. The server was on a Sloaris box. All the JVM's in this setup are 1.5.0_09.