Port connections or secured server
You can encounter a variety of issues with port connections and secured servers. Issues
include, among others, long delays when establishing RMI connections or administrative console login
failures when running in secure mode.
- 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. - Limitations of desktop firewalls
If you are running a desktop firewall that blocks access to your systems ports, you might receive warnings or errors when you are starting servers, or the servers might fail to start. To work around the problem, you must give TCP/IP port access to the server process and use a SOAP connection. - 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. - The internal browser cannot display the administrative console for a secured WebSphere Application Server
On a Linux Motif platform, a blank web page might display on an internal browser when you run the administrative console for a secured WebSphere Application Server. The internal web browser is the default set browser that comes with the workbench. - Administrative console login fails when running in secure mode
- Problems working with a secured server using SSL connections
How to work around the SSLSocketFactory and SSLHandshakeException error messages when you are trying to communicate to a secured server by using a Secure Sockets Layer (SSL) connection within the workbench. - 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
Feedback