are you trying to setup tomcat to serve only jsp pages or all pages in a context
(including html)? if you're serving all pages, try opening a page by giving the
complete url. if you still get a 404 message, it means that you haven't set-up tomcat
to communicate with IIS properly. try checking the registry keys.
if you're setting up tomcat to serve only the jsp pages and IIS to serve the html
pages in the context, you need to add a virtual directory to IIS. Use the context name
as the virtual directory name and it should point to where the context is located. You
can use the IIS Console Manager to do this. Stop and Stop IIS and see if it works.
Hope this helps.
--
On Mon, 18 Dec 2000 15:05:23
Carles Pi-Sunyer wrote:
>Hi,
>
>I've been struggling for the last few days to integrate tomcat 3.2 with IIS.
>My current situation is that I am getting the green up arrow for the filter,
>but I'm getting 404 messages for the pages I'm requesting.
>
>I've tried the following advice without success:
>1) use short directory names.
>2) use the 3.1 workers.properties and uriworkermap.properties files
>3) put the isapi_redirect.dll in a directory under the inetpub directory
>4) reboot NT after changes
>
>My IIS log files show this entry after a request:
>
>20:17:11 127.0.0.1 GET /jakarta/isapi_redirect.dll+ 404
>
>this is a little different then if I request a page that doesn't exist:
>
>22:56:34 127.0.0.1 GET /notthere.html 404
>
>What does the "+" after the isapi_redirect.dll mean?
>
>Any other suggestions on getting this working?
>
>Thanks,
>Carles
>
>Carles Pi-Sunyer
>Stario, Inc.
>http://www.stario.com
>[EMAIL PROTECTED]
>408 844-8333 ex:326
>
>
Get FREE Email/Voicemail with 15MB at Lycos Communications at http://comm.lycos.com
