WebContainer/Servlet Engine problems

Steps to help resolve Common WebContainer/Servlet Engine problems

1. My WebApplication is not started on a server startup
Verify server logs for any error messages during web application initialization.
If the server fails to load the deployment descriptor, verify that the contents ofweb.xml do not containany syntax problems.
If the server log contains any exceptions during servlet initialization, address those problems or turn off load-on-
2. startup for failing servlets.
Static content in WebApplication cannot be served:
Make sure that the URL in the request corresponds to a static resource in the web application.
Verify that the "File Serving" feature is enabled in IBM Extensions. You can verify this by opening thefailing war file in AAT/ASTK/RAD. You can also look for the fileServingEnabled property in ibm-web-ext.xmi file.
3. Users get an HTTP 404 error, or the "VirtualHost/WebGroup Not Found" error is written in the log:
Make sure that the requested URL corresponds to a resource in the web application. This resource canbe a servlet defined in web.xml or a file in the war file.
Verify that the requested URL can be mapped to a Virtual Host alias that is mapped for the failing webapplication. You can verify this by opening the web application details in the administrative console.
If you have a multiple server configuration with multiple virtual hosts, make sure that the plug-in is directing the failing request to the correct application server. Conflicting entries in virtual host aliases may result in sending requests to the wrong application server or mapping to the wrong web application. You should always specify unique entries in host aliases for all virtual hosts present in a particular cell.
4. Users get an HTTP 500 error:
Verify the server logs for detailed messages about the failure and address them.
If the exception is related to the application, it should be addressed by application developers.
If the exception does not provide detailed information, but only contains ServletException, then verify FFDC logs that were created at the time of the exception for additional clues about failure.