Limitations and troubleshooting tips for Server tools
This file contains a comprehensive list of permanent limitations and troubleshooting tips for the Server tools.
Content
Important: Applicable to WebSphere®
Application Server traditional
The limitations and troubleshooting tips that you might
encounter while you are working with the server are divided into the
following sections.
General workbench issues
- Troubleshooting if a problem is related to the workbench or the application server
- Limitations of servers due to invalid characters
- Limitations of server target validation
- Limitation of WebSphere Application Servers when workspace path begins with a backslash
- Limitation on the workbench to work with a WebSphere Application Server that changed its host name
- Limitations of servers due to long directory names
- The server might not stop completely when stopping the server from the Servers view
- A timeout error display when starting the server immediately after the server displays Stopped
- Limitations of X on Linux when using WebSphere Application Server
- Workspace migration limitation
- Web project wizard limitation
Port connections or secured server
- Server port in use when restarting development environment
- Limitations of desktop firewalls
- Long delays when establishing RMI connection after losing network connectivity
- The internal browser cannot display the administrative console for a secured WebSphere Application Server
- Administrative console login fails when running in secure mode
- Problems working with a secured server using SSL connections
- Unable to connect to a remote WebSphere Application Server hosted on a Red Hat Enterprise Linux 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
Adding, removing, or publishing applications to the server
- Troubleshooting if a problem is related to the workbench or the application server
- Limitation on Java 2 security application policy on WebSphere Application Servers
- Removing EJB module shared in multiple EAR projects
- Limitations of Microsoft SQL Server JDBC driver when publishing to a remote WebSphere Application Server
- Publishing fails with duplicate class error
- Unable to use the workbench to publish the same application that was installed using the Administrative Console
WebSphere Application Server profile
Using the administrative console
- The internal browser cannot display the administrative console for a secured WebSphere Application Server
- Administrative console login fails when running in secure mode
- Unable to use the workbench to publish the same application that was installed using the Administrative Console
- Must restart server after changing the WebSphere Application Server configuration