I would rule out an IIS5 issue as the cause of your problem.  I use it constantly and it works with tomcat better than IIS4 does.

The 404 error has two flavours:  If it is the standard 404 error page the you get when you hit an IIS url theat doesn't exist, then your isapi redirector is configured incorrectly.  This is usually frustratingly hard to spot.  You will need to go over all of the configuration steps and double check for typos.  (Also check that the dll is successfully loaded in IIS.)

If the 404 error page is the one served up by tomcat (bigger, bolder font and less verbose,) then the issue probably just what the troubleshooting section says.

Also check you uriworkermap.properties file.  If you are using the 'advanced context configuration' for the examples context, then your URI patterns may not match html files.  E.g. your context entry looks like this:

/examples/servlet/*=ajp12
/examples/*.jsp=ajp12

As you can see, the above patterns do not match files with a .html extension.  You should create a virtual directory in IIS which maps to the root of your examples context, so that IIS can find the html files and serve them up if you want to use this configuration.


Good luck

Cheers.

-----------------------------------------------------------------------------------------------
Aaron Knauf
Implementation Consultant
Genie Systems Ltd
Auckland, New Zealand
Ph. +64-9-573 3310 x812, email: [EMAIL PROTECTED]
http://www.geniesystems.com
------------------------------------------------------------------------------------------------



"Conrad Gustafson" <[EMAIL PROTECTED]>

09/02/2001 12:48
Please respond to tomcat-user

       
        To:        <[EMAIL PROTECTED]>
        cc:        
        Subject:        tomcat-iis-howto




Hi  there,
 
Question:  has  anybody set up tomcat to work with IIS 5.0?  I've done everything right and  it just doesn't work.  When I try to hit http://localhost/examples/jsp/index.html  I get the standard HTTP 404 error page.  The troubleshooting section just  says "make sure you typed the url correctly".
 
Could this be an IIS  5.0 issue?
 
Thanks so  much,
 
Conrad  Gustafson
eXI  Solutions
Victoria,  BC

Reply via email to