| Skip Navigation Links | |
| Exit Print View | |
|
Oracle GlassFish Server 3.1 Troubleshooting Guide |
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?
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
The Administration Console provides a graphical interface for administrative functions. If the Administration Console is not accessible, check the following:
For more information about the Administration Console, see Administration Console in Oracle GlassFish Server 3.1 Administration Guide.
The server must be running before the Administration Console can be accessed.
Review the information in Did the Server Start? to determine if the server is running.
The default port number for the Administration Console is 4848. However, it could be running on a different port number than expected, either because it was intentionally installed there, or because that port was in use when the server was started.
Refer to Was the Server Started at the Expected Port? for guidelines on verifying the port on which the Administration Console is running. Be sure to enter the correct port number and HTTP protocol when invoking the Administration Console.
|