DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12156>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12156 Apache and Tomcat 3.3.1 Interworking problem Summary: Apache and Tomcat 3.3.1 Interworking problem Product: Tomcat 3 Version: 3.1.1 Final Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Critical Priority: Other Component: Connectors AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Here is a problem in the interworking of Apache Web Server and Tomcat Servlet/JSP engine. We are using Apache 1.3.22 and Tomcat 3.3.1 on Windows 2000 and running them as Windows Services. Our web application is successfully deployed in Tomcat in a standard way i.e. in the %TOMCAT_HOME% \webapps directory. Apache web server can be contacted directly without any problems. Trying to access one of the servlets running in Tomcat via Apache using ajp13 �worker�, leads to no response at all. However with the same configuration if we try to access servlet using ajp12 �worker� we get our desired response. There is no error reported in the ap_mod_jk.log file. In case of ajp13 the last entry is: [jk_ajp13_worker.c (610)]: send_request 2: request body to send 0 - request body to resend 0 This gives a hint that the request was sent but no response was received or the request was never sent. However in case of ajp12 after inspecting the ap_mod_jk.log file one can observe that there is a response back from the Tomcat. Here is the snippet of ap_mod_jk.log in case of ajp12: [jk_ajp12_worker.c (357)]: Into ajpv12_handle_request [jk_ajp12_worker.c (361)]: ajpv12_handle_request, sending the ajp12 start sequence [jk_ajp12_worker.c (413)]: ajpv12_handle_request, sending the headers [jk_ajp12_worker.c (432)]: ajpv12_handle_request, sending the terminating mark [jk_ajp12_worker.c (477)]: ajpv12_handle_request done [jk_ajp12_worker.c (148)]: In jk_endpoint_t::service, sent request [jk_ajp12_worker.c (493)]: Into ajpv12_handle_response [jk_ajp12_worker.c (507)]: ajpv12_handle_response, read Status: 200 OK [jk_ajp12_worker.c (535)]: ajpv12_handle_response, read Status=200 OK [jk_ajp12_worker.c (507)]: ajpv12_handle_response, read Content-Type: text/html [jk_ajp12_worker.c (535)]: ajpv12_handle_response, read Content-Type=text/html [jk_ajp12_worker.c (547)]: ajpv12_handle_response, allocating header arrays [jk_ajp12_worker.c (507)]: ajpv12_handle_response, read Set-Cookie: JSESSIONID=jqrjfqw0l1;Path=/apmQuery [jk_ajp12_worker.c (535)]: ajpv12_handle_response, read Set- Cookie=JSESSIONID=jqrjfqw0l1;Path=/apmQuery [jk_ajp12_worker.c (507)]: ajpv12_handle_response, read Servlet-Engine: Tomcat Web Server/3.3.1 Final ( JSP 1.1; Servlet 2.2 ) [jk_ajp12_worker.c (535)]: ajpv12_handle_response, read Servlet-Engine=Tomcat Web Server/3.3.1 Final ( JSP 1.1; Servlet 2.2 ) [jk_ajp12_worker.c (507)]: ajpv12_handle_response, read [jk_ajp12_worker.c (509)]: ajpv12_handle_response, headers are done [jk_ajp12_worker.c (568)]: ajpv12_handle_response, starting response [jk_ajp12_worker.c (579)]: ajpv12_handle_response, reading response body [jk_ajp12_worker.c (595)]: ajpv12_handle_response, response body is done [jk_ajp12_worker.c (607)]: ajpv12_handle_response done [jk_ajp12_worker.c (163)]: Into jk_endpoint_t::done Interestingly if we try to access our servlet directly from Tomcat, the desired response is generated. Our question is as follows: Is there a bug in Tomcat 3.3.1 that prevents it to work with ajp13? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
