Troubleshoot testing and first time run problems
Select the problem you are having with testing or the first run of deployed code for WebSphere Application Server:
- The server process does not start or starts with errors.
- The application does not start or starts with errors.
- A web resource does not display.
- Cannot access a data source.
- Cannot access an enterprise bean from a servlet, a JSP file, a stand-alone program, or another client.
- Cannot look up an object hosted by WAS from a servlet, JSP file, or other client.
- Access problems after enabling security.
- Errors after enabling security.
- Errors after configuring or enabling Secure Sockets Layer.
- Errors in messaging.
- Errors returned to a client sending a SOAP request.
- A client program does not work.
- Errors connecting to WebSphere MQ and creating WebSphere MQ queue connection factory.
If you do not see a problem that resembles yours, or if the information provided does not solve your problem, see Obtaining help from IBM.
For current information available from IBM Support on known problems and their resolution, see the IBM Support page.
IBM Support has documents that can save you time gathering information needed to resolve this problem. Before opening a PMR, see the IBM Support page.
Related Tasks
Troubleshooting by task
Troubleshooting by component
See Also
The server process does not start or starts with errors
The application does not start or starts with errors
A web resource does not display
Cannot access a data source
Cannot access an enterprise bean from a servlet, a JSP file, a stand-alone program, or another client
Cannot look up an object hosted by WAS from a servlet, JSP file, or other client
Access problems after enabling security
Errors after enabling security
Errors after configuring or enabling Secure Sockets Layer
Errors in messaging
Errors returned to a client sending a SOAP request
A client program does not work
Errors connecting to WebSphere MQ and creating WebSphere MQ queue connection factory