Application deployment troubleshooting tips
When you first test or run a deployed application, you might encounter problems. Select the problem you are having with testing or the first run of deployed code for WAS:
- Server startup problems.
- Application startup problems.
- Web resource is not displayed.
- Data access problems.
- Enterprise bean cannot be accessed from a servlet, a JSP file, a stand-alone program, or another client.
- Application access problems.
- Access problems after enabling security.
- Security enablement followed by errors.
- Secure Sockets Layer errors.
- Messaging errors.
- Application client sending SOAP request receives errors.
- A client program does not work.
- WebSphere MQ connection and queue connection factory creation errors.
If you do not see a problem that resembles yours, or if the information provided does not solve your problem, see Troubleshooting 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 Must gather documents page for information to gather to send to IBM Support page.
Related concepts
Troubleshoot_and_support3240.html
Related tasks
Deploying and administering J2EE applications
Related Reference
Server startup problems
Application startup problems
Web resource is not displayed
Data access problems
Enterprise bean cannot be accessed from a servlet, a JSP file, a stand-alone program, or another client
Application access problems
Access problems after enabling security
Security enablement followed by errors
Secure Sockets Layer errors
Messaging errors
Application client sending SOAP request receives errors
A client program does not work
WebSphere MQ connection and queue connection factory creation errors
Reference topic