1. Overview of Oracle GlassFish Server Troubleshooting
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
When this error occurs, check the following:
If the console window is still open, the expected message indicates that the default domain was started successfully.
If the console window is already closed, check for messages in the log file:
as-install/domains/domain1/logs/server.log
If startup was successful, the expected message is similar to that on the console, and appears at the end of the log file.
For more information about starting a domain, see Starting and Stopping a Domain in Oracle GlassFish Server 3.1 Administration Guide. To easily determine if a domain is running, use the asadmin list-domains command.
The server might be running at a different port number than expected, either because it was intentionally installed there, or because another server was already running on the default port when the server was installed.
as-install/domains/domain1/config/domain.xml
Be sure to enter the correct port number when invoking the server.
Issues might result when personal firewalls are enabled. Disable your personal firewall and see if the server access problem still exists.