Server Tools limitations and restrictions with WebSphere Application Server v6.x
This section describes known limitations and problems along with suggested workarounds for the Server Tools with WebSphere
®
Application Server v6.x.
Limitations of servers due to invalid characters
Limitation on Java 2 security application policy on WebSphere Application Servers
A restricted or standard user fails to start the server
Limitation of the initial status on the Servers view
Limitation on switching target server for an EJB project
Limitations of server target validation
Limitation of WebSphere Application Servers when workspace path begins with a backslash
Server port in use when restarting development environment
Console output of WebSphere Application Server V6.0 displays old logs
Limitation on WebSphere Application Server v6.0 console output (Linux only)
Links on the JNDI Explorer view of the Universal Test Client do not display
Limitation on the workbench to work with a WebSphere Application Server that changed its host name
Limitation using a SOAP connection type for a long period of time
Limitations of desktop firewalls
Limitations of servers due to long directory names
The internal browser cannot display the administrative console for a secured WebSphere Application Server v6.x
Console output does not display for remote WebSphere Application Server v6.x
Problems publishing to a WebSphere Application Server Network Deployment v6.x
Removing EJB module shared in multiple EAR projects
Creating profiles for WebSphere Application Server under a 64 bit machine
Long delays when establishing RMI connection after losing network connectivity
Running multiple threaded WebSphere application clients
The server might not stop completely when stopping the server from the Servers view
Feedback