I am exceedingly ignorant in the J2EE universe, but I did manage to get
TC5.5 talking to IIS 6 effectively (3 times, so it wasn't a fluke!).

Have you seen this doc:
http://jakarta.apache.org/tomcat/connectors-doc/howto/iis.html

It has some troubleshooting info.

Be sure to at least restart the IIS service, probably even reboot
entirely!

Tracy

-----Original Message-----
From: David Thielen [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, September 06, 2005 4:29 PM
To: tomcat-user@jakarta.apache.org
Subject: Connectiong tomcat to IIS - no luck and conflicting info

Hi;

 

I am trying to connect Tomcat 5.5 to IIS 5.1 and having zero luck.

 

Here is what I did:

1.      Went to
http://apache.towardex.com/jakarta/tomcat-connectors/jk/binaries/win32/j
k-1.
2.14
2.      Downloaded & ran isapi_redirect-1.2.14.exe
3.      Added isapi_redirect as an ISAPI filter to the default website.

 

When I try to bring up the page http://localhost/jkstatus I get the
following in my IIS log:

20:19:47 127.0.0.1 GET /jkstatus 404

 

So it's not even calling isapi_redirect.dll. The installer did create
the
jakarta virtual directory and some registry entries. (I believe that
even if
all of my tomcat settings are wrong - it should still be calling
isapi_redirect.)

 

I'm stuck now. The book Pro Jakarta Tomcat 5 discusses setting this up
using
isapi_redirect2.dll and using registry entries that have a 2.0 node in
them.
But I can't find any metion of this anywhere else.

 

The isapi_redirect installer doesn't have any documentation.

 

On the jakarta website I can't find any 5.x specific install
instructions.

 

I've done this successfully for Tomcat 4.x - see
http://dave.thielen.com/articles/Configuring%20Tomcat%20to%20work%20with
%20I
IS.doc but these instructions don't match the contents of the config
files
for 5.5.

 

So what should I try next?

 

Thanks - dave

 




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to