From a thread in the GlassFish forums on java dot net
What I use:
- Mac OS 10.6 with latest updates installed on my local machine
- Netbeans 6.9 + Glassfish 3.0.1 (local installation ==> works fine)
- Glassfish 3.0.1 Remote Server on Ubuntu Server (Hardy)
- Ubuntu Firewall is open
- Remote Port is 4848 and only accessable via https
Here is what I try in detail in Netbeans for setting up the Remote Server:
1. Choose Tools -> Servers in the menu bar
2. Click on "Add Server..." button
3. Choose "Glassfish Server 3" in the opening dialog
4. Click on "next" button
5. Choose the local installation location of the local Glassfish 3.0.1 installation (for me: "/Applications/NetBeans/glassfish-3.0.1")
6. Click on "next" button
7. Choose radio button "Register Remote Domain"
8. Enter the remote hostname: (i.e, mydomain.com)
9. Enter the corresponding admin port (i.e. 4848)
10. now click on "finish" button
After this I can see the following in my Server list for the Server I just added:
- Location : "mydomain.com:8080"
- Domain Folder : ""
- Domain Name : ""
- Checkboxes set: "Preserver Sessions Across Redeployment" (editable checkbox) + "Enable JDBC Driver Deployment" (non editable checkbox), all other checkboxes are disabled and not set
As you see both Domain Folder and Domain Name is empty.
Furthermore I cannot change any of Location, Domain Folder or Domain Name settings anymore (==> non editable fields).
Now I should actually be able to connect to the server, start it, stop it, etc.
What I do to test this:
11. Go to the "Services" tab on the left sinde of Netbeans IDE
12. Open the "Servers" list (as I see my remote Glassfish server I just added is listed besides my local Glassfish server)
13. Right-Click on the remote Server:
- Start, Stop, Restart, etc. is disabled ==> I cannot start it from Netbeans
- Refresh is enabled, but doesn't change anything
- Clicking on "View Admin Console" leads to the message: "The server must be running for this actoin to succeed."
- In the properties I cannot change anything (see above)
I was able to replicate this issue.
In my situation, the hostname for the cert does match the hostname of the connection... so the connection is not acceptable and this trickles up to the test to see if a server is running.
Integrated into 'main-golden', will be available in build *201007220001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Vince Kraemer <firstname.lastname@example.org>
Log: #188799: hostname mismatches thwart the 'is this server running?' check