Server connections
You can encounter a variety of issues with server connections. Issues include, among others, long delays when establishing RMI connections or the server port being in use when you restart your development environment.
- Server port in use when you are restarting the development environment
If the product crashes or the Java™ product process is stopped externally, such as in the Windows Task Manager, while the server is running, you might receive a Server port port_number is in use message when you try to start the server after you restart the development environment. Some server resources are not fully released. - Long delays when establishing RMI connection after losing network connectivity
On Windows operating systems, if you are using the remote method invocation (RMI) port to connect to your WebSphere® Application Server, you might experience long delays to establish a connection to the server after you lose network connectivity. This can occur even if the server is local and the network connectivity is lost only temporarily, which is common in a wireless network environment. If you know that the server is started, but the status in the Servers views displays Stopped or Started, try to see if you can establish a connection to the server by switching the server connection from RMI to SOAP. The status of the server changes to Started. - Unable to connect to a remote WebSphere Application Server hosted on a Red Hat Enterprise Linux machine
This topic discusses the steps that you must configure on a Red Hat Enterprise Linux 5 to set up the host name for accessing the WebSphere Application Server from a remote machine. - Server connection or publishing problems when connecting to a remote WebSphere Application Server
- Unable to bind to ports on a Linux operating system after restarting the server
Parent topic: Limitations and troubleshooting tips for Server tools

