Troubleshooting
Problem
Problem Description: JSP requests were blocked at the IBM WebSphere HTTP Plugin and not properly reaching the WebSphere Application Server. In this case, the Plugin responds with a 500 Internal Server Error response code. As seen in the logs: The WebSphere HTTP Plugin did not handle these requests, because another module returned 500 before the Plugin could send the request to WebSphere Application Server: See these back-to-back messages: 1> From IBM HTTP Server Access log (access.log): 199.159.192.128 - - [07/Aug/2008:09:54:17 -0500] "GET /Internet/index.jsp HTTP/1.1" 500 663 199.159.192.128 - - [07/Aug/2008:09:54:17 -0500] "GET /Internet/index.jsp HTTP/1.1" 500 663 952 - 2>From Websphere HTTP Plugin Logs (http_plugin.log): [Wed Jul 23 10:26:28 2008] 00003965 b7f326c0 - TRACE: mod_was_ap20_http: as_translate_name: WebSphere will handle: /Internet/index.jsp [Wed Jul 23 10:26:30 2008] 00003965 b7f326c0 - TRACE: mod_was_ap20_http: in as_logger as_handle() was never called, because another Apache module returned 500 likely during authentication (between mapping the URL to a file and actually running the content generator)
Symptom
Request for JSP worked when bypassing the plug-in. Returned http error 500 when sent by way of the plug-in.
Cause
In this case, the httpd.conf file had the following directive loaded:
| # # Load config files from the config directory # "/etc/httpd/conf.d". # Include conf.d/*.conf |
| # # Root context mounts for Tomcat # # # e e commented out for WebSphere JkMount /*.jsp ajp13 JkMount /servlet/* ajp13 |
Environment
RedHat Linux ES4
Resolving The Problem
JkMount directives in tertiary file loaded from httpd.conf file was causing the blocking of all JSP files from reaching the as_handler() code in the plug-in.
Commenting out the JkMount directives (in /etc/httpd/conf.d/mod_jk.conf) resolves the issue. For example:
| #JkMount /*.jsp ajp13 #JkMount /servlet/* ajp13 |
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21316166