| 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?
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?
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
This problem occurs on Windows XP systems with GlassFish Server software, and is due to a known Windows security flaw rather than a problem with GlassFish Server itself.
The problem occurs when two or more instances of GlassFish Server are created using the same port number for the instanceport option; for example:
asadmin create-domain -adminport 5001 options -instanceport 6001 domain asadmin create-domain -adminport 5002 options -instanceport 6001 domain
When the two domains are started on a UNIX or Linux system, a port conflict error is thrown and the second instance fails to start. However, when the two domains are started on Windows XP, no error is thrown, both server instances start, but only the first instance is accessible at the specified port. When that first server instance is subsequently shut down, the second instance then becomes accessible. Moreover, when both instances are running, the Windows netstat command only reports the first instance.
Be sure to use unique port numbers for all server instances on Windows systems.
|