WebSphere HTTP and Servlet Processing

HTTP and Servlet Processing on WebSphere Application Server WebSphere Support Team technical resolutions to common problems with HTTP and Servlet Processing.

Support Help

Web Related Issues

When HTTP Requests are sent to WebSphere Application server, they are handled by the Web Container for routing to the correct application, web module, and servlet. Processing is then handed off to the servlet being requested. Once processing is complete, the Web Container generates and returns the HTTP Response to the client.

When dealing with HTTP related issues, the first step is recognizing the error in question, whether it be an HTTP error status (such as a 404 File Not Found or 500 Internal Server Error) , an abnormality in page functionality (such as an incorrect or blank page being returned), or an issue with redirection (redirecting to the wrong page).

If other devices such as a web server or the WebSphere plugin exist in front of the application server, the issue could also reside in one of these devices.

Once the problem is identified and located, appropriate steps may be taken to begin debugging and narrow down the problem.

MustGathers

MustGather: Web container problems in WebSphere Application Server and WebSphere Liberty

MustGather: Request failures accessing WebSphere Application Server dynamic content through IBM HTTP Server

“IBM prides itself on delivering world class software support with highly skilled, customer-focused people. ”

Return to 101 home

Contact Support