Thanks for your advice but I'm afraid all the tomcat logs seem to be in
order to me. Does anyone have any idea what might be causing this problem?
Thanks again,
Hamish
--console---
2001-06-11 01:53:01 - Ctx( ): 404 R( + /jakarta/isapi_redirect.dll + null)
null
--jasper.log---
2001-06-11 11:44:56 - JspEngine --> /contact.jsp
2001-06-11 11:44:56 - ServletPath: /contact.jsp
2001-06-11 11:44:56 - PathInfo: null
2001-06-11 11:44:56 - RealPath:
C:\tomcat\jakarta-tomcat-3.2.1\webapps\conference\contact.jsp
2001-06-11 11:44:56 - RequestURI: /conference/contact.jsp
2001-06-11 11:44:56 - QueryString: null
2001-06-11 11:44:56 - Request Params:
2001-06-11 11:44:56 - Classpath according to the Servlet Engine is:
C:\tomcat\jakarta-tomcat-3.2.1\webapps\conference\WEB-INF\classes;C:\tomcat\
jakarta-tomcat-3.2.1\webapps\conference\WEB-INF\lib\addressTags.jar;C:\tomca
t\jakarta-tomcat-3.2.1\webapps\conference\WEB-INF\lib\viewclasses.jar;C:\tom
cat\jakarta-tomcat-3.2.1\webapps\conference\WEB-INF\lib\viewsClasses.jar
--servlet.log---
2001-06-11 11:46:39 - path="/conference" :jsp: init
-----Original Message-----
From: Randy Layman [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 11, 2001 1:44 PM
To: [EMAIL PROTECTED]
Subject: RE: Problems with Tomcat/IIS5
The problem is with your Tomcat configuration - AJP12 is reading a
404 from the connector (about 1/2 way through your log entry). Check out
your Tomcat configuration, specifically look that /conference is either a
webapp or a directory from the ROOT context, but the Tomcat logs should give
you more information about what is going wrong.
Randy
> -----Original Message-----
> From: Hamish Barney [mailto:[EMAIL PROTECTED]]
> Sent: Monday, June 11, 2001 8:12 AM
> To: '[EMAIL PROTECTED]'
> Subject: Problems with Tomcat/IIS5
>
>
> Just wondering if anyone else has had the same experience and
> if they were
> able to resolve it.
>
> Trying to get Tomcat 3.2.1 working with IIS5 but I seem to
> have issues with
> the ISAPI redirector. I've used exactly the same
> configuration with IIS4 on
> a different machine and it works perfectly. However I always
> get a 404 error
> when I try to request files when I try with IIS5. I used the
> same file to
> create both sets of registry settings and as the same
> uriworkermap.properties file on both machines.
>
> The log from the isapi redirector is shown below. It appears
> to find the
> jsp, contact.jsp that is requested but still sends back a 404
> error. Is
> anyone aware of any differences between IIS4 and IIS5 that
> might produce an
> error like this your help would be greatly appreciated.
>
> Thanks,
> Hamish
>
>
> --ISAPI Redirector Log-----
> [jk_isapi_plugin.c (408)]: HttpFilterProc started
> [jk_isapi_plugin.c (429)]: In HttpFilterProc test redirection of
> /conference/contact.jsp
> [jk_uri_worker_map.c (344)]: Into
> jk_uri_worker_map_t::map_uri_to_worker
> [jk_uri_worker_map.c (406)]:
> jk_uri_worker_map_t::map_uri_to_worker, Found a
> match ajp12
> [jk_isapi_plugin.c (439)]: HttpFilterProc
> [/conference/contact.jsp] is a
> servlet url - should redirect to ajp12
> [jk_isapi_plugin.c (461)]: HttpFilterProc check if
> [/conference/contact.jsp]
> is points to the web-inf directory
> [jk_isapi_plugin.c (408)]: HttpFilterProc started
> [jk_isapi_plugin.c (429)]: In HttpFilterProc test redirection of
> /jakarta/isapi_redirect.dll
> [jk_uri_worker_map.c (344)]: Into
> jk_uri_worker_map_t::map_uri_to_worker
> [jk_uri_worker_map.c (434)]:
> jk_uri_worker_map_t::map_uri_to_worker, done
> without a match
> [jk_isapi_plugin.c (452)]: HttpFilterProc
> [/jakarta/isapi_redirect.dll] is
> not a servlet url
> [jk_isapi_plugin.c (461)]: HttpFilterProc check if
> [/jakarta/isapi_redirect.dll] is points to the web-inf directory
> [jk_isapi_plugin.c (517)]: HttpExtensionProc started
> [jk_worker.c (123)]: Into wc_get_worker_for_name ajp12
> [jk_worker.c (127)]: wc_get_worker_for_name, done found a worker
> [jk_isapi_plugin.c (539)]: HttpExtensionProc got a worker for
> name ajp12
> [jk_ajp12_worker.c (223)]: Into jk_worker_t::get_endpoint
> [jk_ajp12_worker.c (121)]: Into jk_endpoint_t::service
> [jk_connect.c (108)]: Into jk_open_socket
> [jk_connect.c (115)]: jk_open_socket, try to connect socket = 1296
> [jk_connect.c (124)]: jk_open_socket, after connect ret = 0
> [jk_connect.c (132)]: jk_open_socket, set TCP_NODELAY to on
> [jk_connect.c (140)]: jk_open_socket, return, sd = 1296
> [jk_ajp12_worker.c (134)]: In jk_endpoint_t::service, sd = 1296
> [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 (472)]: ajpv12_handle_request done
> [jk_ajp12_worker.c (148)]: In jk_endpoint_t::service, sent request
> [jk_ajp12_worker.c (488)]: Into ajpv12_handle_response
> [jk_ajp12_worker.c (502)]: ajpv12_handle_response, read
> Status: 404 Not
> Found
> [jk_ajp12_worker.c (530)]: ajpv12_handle_response, read
> Status=404 Not Found
> [jk_ajp12_worker.c (502)]: ajpv12_handle_response, read Content-Type:
> text/html
> [jk_ajp12_worker.c (530)]: ajpv12_handle_response, read
> Content-Type=text/html
> [jk_ajp12_worker.c (542)]: ajpv12_handle_response, allocating
> header arrays
> [jk_ajp12_worker.c (502)]: ajpv12_handle_response, read
> Content-Length: 201
> [jk_ajp12_worker.c (530)]: ajpv12_handle_response, read
> Content-Length=201
> [jk_ajp12_worker.c (502)]: ajpv12_handle_response, read
> Servlet-Engine:
> Tomcat Web Server/3.2.1 (JSP 1.1; Servlet 2.2; Java 1.3.0_02;
> Windows 2000
> 5.0 x86; java.vendor=Sun Microsystems Inc.)
> [jk_ajp12_worker.c (530)]: ajpv12_handle_response, read
> Servlet-Engine=Tomcat Web Server/3.2.1 (JSP 1.1; Servlet 2.2;
> Java 1.3.0_02;
> Windows 2000 5.0 x86; java.vendor=Sun Microsystems Inc.)
> [jk_ajp12_worker.c (502)]: ajpv12_handle_response, read
> [jk_ajp12_worker.c (504)]: ajpv12_handle_response, headers are done
> [jk_ajp12_worker.c (563)]: ajpv12_handle_response, starting response
> [jk_isapi_plugin.c (201)]: Into jk_ws_service_t::start_response
> [jk_ajp12_worker.c (574)]: ajpv12_handle_response, reading
> response body
> [jk_isapi_plugin.c (335)]: Into jk_ws_service_t::write
> [jk_ajp12_worker.c (590)]: ajpv12_handle_response, response
> body is done
> [jk_ajp12_worker.c (602)]: ajpv12_handle_response done
> [jk_isapi_plugin.c (551)]: HttpExtensionProc service() returned OK
> [jk_ajp12_worker.c (163)]: Into jk_endpoint_t::done
>
