
Two Server Instances Bind to Same Port on Windows
Is Another Application Running on the Server's Port?
If another application is using the server's port, stop the other application, then restart
Enterprise Server.
Has an Ungraceful Shutdown Occurred on a Previously Running Server?
Use the asadmin
Two Server Instances Bind to Same Port on Windows
Description
This problem only occurs on Windows 2000/XP systems with Enterprise Server software, and is due to a known Windows security flaw rather than a problem with Enterprise Server itself.
The problem occurs when two or more instances of Enterprise Server are created using the same port number for the instanceport option; for example:
asadmin
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 2000/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.
Solution
Be sure to use unique port numbers for all server instances on Windows systems.
28 | Sun GlassFish Enterprise Server v3 Prelude Troubleshooting Guide • November 2008 |