Thanks Jason, Yes I've seen the link and read it a number of times but haven't gotten anywhere. I assume that the problem is in worker.properties but still can't find just what it is. I suppose it could be one of those stupid typos that you look at 50 times before recognizing but I'm sure I've looked at least 49 so far. (I'm using also worker rather than workers2 because I believe that should work with Tomcat 4.1.12. by the way. I've considered changing to workers2 but that could open up a whole new can of worms.)
I did compare my logs to an old log that was working until I upgraded Tomcat. In that log there's no attempt to map isapi_redirector.dll so I figure that must be where things are going wrong. Thanks for the link to the source. I'm hoping I'll find the answer there. Ken -----Original Message----- From: Jason Bainbridge [mailto:[EMAIL PROTECTED] Sent: Monday, June 23, 2003 1:31 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense What entries have you got in your workers2.properties? Sounds like something is wrong with your setup... I'm assuming you have seen this howto? http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk2/installhowto.html As for making sense of the process, gotta love open source: http://tinyurl.com/f1lo Nothing beats reading the source itself. :) Regards, -- Jason Bainbridge http://jblinux.org On Tue, 24 Jun 2003 01:19, Januski, Ken wrote: > but I've yet found any sensible explanation of hooking up IIS and Tomcat. I > have found step by step instructions but not any explanations. What's more > embarrassing is that I posted a similar IIS/Tomcat problem 3-4 months ago, > finally solved it, and now I've upgraded Tomcat and have it again. > > Though there are a number of howtos on getting IIS and Tomcat working > together I'm still looking for some help in making sense of the actual > process, in other words I ought to be able to look at the redirector logs > and figure out what the problem is, or at least where to start looking. The > redirector logs seem to be full of useful information and yet I see > numerous people posting messages here asking for help with them. So I guess > what I'm asking is if there is any resource that can help explain the logs. > I'd really like to just read them and diagnose the problem based on that. > Can anyone point me to such a resource? > > I believe that my current problem is that Tomcat is trying to map the > redirector when it should be doing something else. So I'm getting log > entries that say: > > [jk_isapi_plugin.c (759)-- Jason Bainbridge http://jblinux.org]: In HttpFilterProc Virtual Host redirection of > /inqtomcat/jakarta/isapi_redirector.dll > [jk_uri_worker_map.c (460)]: Into jk_uri_worker_map_t::map_uri_to_worker > [jk_uri_worker_map.c (477)]: Attempting to map URI > '/inqtomcat/jakarta/isapi_redirector.dll' > [jk_uri_worker_map.c (599)]: jk_uri_worker_map_t::map_uri_to_worker, done > without a match > [jk_isapi_plugin.c (765)]: In HttpFilterProc test Default redirection of > /jakarta/isapi_redirector.dll > [jk_uri_worker_map.c (460)]: Into jk_uri_worker_map_t::map_uri_to_worker > [jk_uri_worker_map.c (477)]: Attempting to map URI > '/jakarta/isapi_redirector.dll' > [jk_uri_worker_map.c (599)]: jk_uri_worker_map_t::map_uri_to_worker, done > without a match > > I'm pretty sure that Tomcat shouldn't be trying to map the dll though > that's just a guess. That's why I believe that if I could find some > explanation of the whole process I could figure out the answer on my own, > and perhaps others could as well, rather than sending so many message here > regarding it. > > By the way I have looked at archives and seen a number of entries that come > close to solving the above problem. But none of them work for me and they > don't really explain what is going on, or if they do I'm just missing it. > As I said I think if I could figure out what is going on in the connector > process that I could figure it out for myself. > > Thanks for any help. > > Ken --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
