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:
- Application server will not start, or starts with errors.
- Application will not start, or starts with errors.
- Web resource does not display.
- Cannot access a datasource.
- Cannot access an enterprise bean from a servlet, JSP file, stand-alone program, or other client.
- Cannot access an object hosted by WAS, such as an enterprise bean or connection pool, from a servlet, JSP file, stand-alone program, or other client.
- Errors and access problems after enabling security.
- Errors after enabling SSL , or SSL-related error messages.
- Problems with messaging.
- Errors when trying to send a SOAP request.
- WAS Client program does not work.
If you do not see a problem that resembles yours, or if the information provided does not solve your problem, contact IBM support for further assistance.
Troubleshooting by component: what is not working?
The appserver or Deployment Manager does not start or starts with errors
The application does not start or starts with errors
Web resource (JSP file, servlet, HTML file, image) does not display
Cannot access a data source
Cannot access an enterprise bean from a servlet, JSP file, stand-alone program, or other client
Cannot look up an object hosted by WAS from a servlet, JSP file, or other client
Errors or access problems after enabling security
Errors after enabling SSL, or SSL-related error messages
Errors in messaging JMS
Errors returned to client trying to send a SOAP request
Client program does not work
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.