1. Overview of Oracle GlassFish Server Troubleshooting
Cannot Access Local Server (http://localhost:8080)
Was the Server Started at the Expected Port?
Is a Personal Firewall Enabled?
Is the Server Available Locally?
Is the Proxy Setting Causing a Problem?
Cannot Access the Administration Console
Is the Application Server Running?
Is the Administration Console Running on the Expected Port?
Cannot Access a Server Application
Is the Application Server Running?
Was Application Deployment Successful?
Administrator User Name or Password Not Known
Experience Issues Related to the JDK
Server Will Not Start on Windows (Port Conflict)
Is Another Application Running on the Server's Port?
Has an Ungraceful Shutdown Occurred on a Previously Running Server?
Two Server Instances Bind to Same Port on Windows
Cannot Produce a JVM Thread Dump After Server Crash
To Obtain a Server Thread Dump
Issues Related to Applications
Cannot Undeploy or Redeploy Application With Open Streams to jar Files (Windows)
asadmin start-domain Command Fails
Cannot Stop Domain Using asadmin stop-domain
Issues Related to Installation
Installation Hangs During Update Tool Configuration
GlassFish Server Components Not Removed During Uninstallation
java.security.AccessControlException: Access Denied Error
Mutual Authentication Not Working With the Application Client
If a message similar to the following is displayed when starting GlassFish Server on Microsoft Windows, a server port conflict has occurred:
Address already in use
This error occurs when another application is running on the GlassFish Server port (default 8080), or because a previous instance of GlassFish Server did not shut down cleanly.
You might also check the following:
If another application is using the server's port, stop the other application, then restart GlassFish Server.
Use the asadmin stop-domain command to stop the server, or explicitly kill the Java process and then restart GlassFish Server.