Hmm. You know I've found references to both worker.properties and workers.properties and haven't found an explanation of why both seem to be used. I believe I've used both names in my lengthy attempts to get this to work. But I'll change it and see what happens.
I've also used the inqtomcat host name in the past when I used Tomcat 4.0 so thought I could use it again. Also I've changed it back to localhost in my many tests but still ran into failures. But I'll also try localhost again just to see. Yes, registry files are consistent with everything else. I'll check them one more time with these new changes and see what happens. -----Original Message----- From: John Turner [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 3:40 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense A couple things: - the file should be workers.properties, not worker.properties - the host parameter has to be something that the redirector can find...so if you aren't using localhost, you are better off with an IP address I'm assuming you made all the registry entries, right? HTH John On Tue, 24 Jun 2003 15:34:40 -0400, Januski, Ken <[EMAIL PROTECTED]> wrote: > Thanks Dom, > > I've wondered about using JK2 but since the ESRI instructions for ArcIMS > say > that JK should work I thought I'd stick with that. I just don't know much > about JK2 so didn't want to perhaps complicate the problem. So for now > I'm > including worker.properties. If that doesn't help I may take you up on > your > offer for your JK2 configuration files. > > # workers.tomcat_home="C:\Tomcat4112" > # workers.java_home="C:\java\jdk1.4" # # ps=\ > # #-------ADVANCED MODE------- #------------------------------ # # #------ > > > -DEFAULT worker list------ #---------------------------------- # #The > worker that your plugins should create and work with # worker.list=ajp13 > # #----DEFAULT ajp13 WORKER DEFINITION----- # #Defining a worker named > ajp13 and of type ajp13 #Note that the name and the type do not have to > match. # worker.ajp13.port=8009 worker.ajp13.host=inqtomcat > worker.ajp13.type=ajp13 #*****End worker.properties***** > > > Thanks to everyone who's spending time on this, > > Ken > > -----Original Message----- > From: Dominic Parry [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 24, 2003 3:30 PM > To: Tomcat Users List > Subject: Re: Connectors for IIS/Tomcat SHOULD make sense > > > Hi Ken > > I have a suggestion. You should try using JK2 instead of JK, ie use > isapi_redirector2.dll. If you want, I can send you all my working configs > for this connector. If you don't want to use it, try posting your > workers.properties file, and we can try to spot that "typo" > > Cheers > > Dom > ----- Original Message ----- From: Januski, Ken To: Tomcat Users List > Sent: Tuesday, June 24, 2003 9:10 PM > Subject: RE: Connectors for IIS/Tomcat SHOULD make sense > > > Hi Jason, > > Yes the green arrow is green and pointing up. I've removed and added both > the filter and the virtual directory many times. I really seem to have no > problem getting it to work. > > I believe that it's Tomcat that is causing the problem as the log > indicates > an ajp13 worker is created. Also most of the various urls I've tried get > a > match in the log. So this indicates to me that the properties files are > being used. So for example my minimal worker.properties has > /examples/*=ajp13. If I use "http://inqtomcat/examples/"; the log shows > that > a match is found in uriworkermap.properties. HttpFilterProc then checks > to > see if it's a servlet, etc. However the log then shows that it tries to > map > "/jakarta/isapi_redirector.dll" and doesn't find a match. I don't think > it > should be trying to match that or map it. Also I've tried /examples or > other > files with inqtomcat:8080 and they work fine. > > So it looks to me like the filter is redirecting from IIS to Tomcat as it > should but Tomcat then is trying to do the wrong thing with the file. > > Ken > > -----Original Message----- > From: Jason Bainbridge [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 24, 2003 2:54 PM > To: Tomcat Users List > Subject: Re: Connectors for IIS/Tomcat SHOULD make sense > > > Lets get back to basics... > > Is the ISAPI plugin showing with a green arrow in IIS indicating it has > been > > loaded successfully? > > What does your uriworkermap.properties file look like? > > What is throwing the 404? Tomcat or IIS? What URL are you trying to > access > > when you get the 404? > > Regards, > -- Jason Bainbridge > http://jblinux.org > > On Wed, 25 Jun 2003 02:27, Januski, Ken wrote: > > Thanks John, > > > > I wasn't sure about the loadbalancing. I commented it out but I'm still > > getting the 404 errors, "/jakarta/isapi_redirector.dll is not > available." > > > > I've watched other people have this error, including someone about a > week > > ago I think, in which you gave some advice. But as far as I can tell > the > > problem was never solved. It's surprising to me how fragile the > IIS/Tomcat > > connectors seem to be. Most of the documentation finally ends with > "this > > should now work. If not please check for typos in worker.properties, > etc." > > Perhaps this really is the right advice and I'll eventually see a typo. > But > > right now it sure doesn't look like there are any to me and it's hard > to > > know where to turn next, other than scouring the web for people who've > had > > similar problems. > > > > I guess what I find oddest is that the logs are full of information but > no > > one seems to know how to interpret them.... But then again I probably > put > > more stock in logs than many people do. > > > > Ken > > > > -----Original Message----- > > From: John Turner [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, June 24, 2003 1:58 PM > > To: Tomcat Users List > > Subject: Re: Connectors for IIS/Tomcat SHOULD make sense > > > > > > > > There's no need for any of the loadbalancing stuff in > workers.properties. > > You only need the four lines: type, name, port, host. > > > > John > > > > On Tue, 24 Jun 2003 13:10:33 -0400, Januski, Ken > <[EMAIL PROTECTED]> > > > > wrote: > > > Another day's experimentation and no more progress. One thing I > notice > is > > > that the source code seems to refer to isapi_redirector2 and I'm > using > > > isapi_redirector.dll. I'm using that because I'm following > instructions > > > from > > > ESRI for preparing IIS and Tomcat for an ArcIMS upgrade. Their > > > instructions > > > indicate that isapi_redirector.dll should work with Tomcat 4.1.12 and > I, > > > at > > > least so far, have no reason to doubt them. > > > > > > I've also edited my worker.properties files to a minimum just for > > > testing. > > > I'm including it below. But I'm still puzzled as to why I'm getting > the > > > 404 > > > error. The log indicates that an ajp13 worker is being created > > > successfully > > > and I don't really see any errors related to it, other than the 404. > > > > > > [Tue Jun 24 12:47:34 2003] [jk_worker.c (132)]: Into > > > wc_get_worker_for_name > > > ajp13 > > > [Tue Jun 24 12:47:34 2003] [jk_worker.c (136)]: > wc_get_worker_for_name, > > > done found a worker > > > [Tue Jun 24 12:47:34 2003] [jk_isapi_plugin.c (860)]: > HttpExtensionProc > > > got > > > a worker for name ajp13 > > > [Tue Jun 24 12:47:34 2003] [jk_ajp_common.c (1352)]: Into > > > jk_worker_t::get_endpoint > > > [Tue Jun 24 12:47:34 2003] [jk_ajp_common.c (1075)]: Into > > > jk_endpoint_t::service > > > [Tue Jun 24 12:47:34 2003] [jk_ajp_common.c (280)]: Into > > > ajp_marshal_into_msgb > > > [Tue Jun 24 12:47:34 2003] [jk_ajp_common.c (413)]: > > > ajp_marshal_into_msgb - > > > Done > > > [Tue Jun 24 12:47:34 2003] [jk_connect.c (116)]: Into jk_open_socket > > > [Tue Jun 24 12:47:34 2003] [jk_connect.c (123)]: jk_open_socket, try > to > > > connect socket = 2600 > > > [Tue Jun 24 12:47:34 2003] [jk_connect.c (132)]: jk_open_socket, > after > > > connect ret = 0 > > > [Tue Jun 24 12:47:34 2003] [jk_connect.c (140)]: jk_open_socket, set > > > TCP_NODELAY to on > > > [Tue Jun 24 12:47:34 2003] [jk_connect.c (148)]: jk_open_socket, > return, > > > sd > > > = 2600 > > > [Tue Jun 24 12:47:34 2003] [jk_ajp_common.c (588)]: In > > > jk_endpoint_t::ajp_connect_to_endpoint, connected sd = 2600 > > > [Tue Jun 24 12:47:34 2003] [jk_ajp_common.c (612)]: sending to ajp13 > > > #294 > > > [Tue Jun 24 12:47:34 2003] [jk_ajp_common.c (853)]: ajp_send_request > 2: > > > request body to send 0 - request body to resend 0 > > > [Tue Jun 24 12:47:34 2003] [jk_ajp_common.c (698)]: received from > ajp13 > > > #81 > > > [Tue Jun 24 12:47:34 2003] [jk_ajp_common.c (461)]: > > > ajp_unmarshal_response: > > > status = 404 > > > [Tue Jun 24 12:47:34 2003] [jk_ajp_common.c (466)]: > > > ajp_unmarshal_response: > > > Number of headers is = 2 > > > [Tue Jun 24 12:47:34 2003] [jk_ajp_common.c (506)]: > > > ajp_unmarshal_response: > > > Header[0] [Content-Type] = [text/html;charset=ISO-8859-1] > > > [Tue Jun 24 12:47:34 2003] [jk_ajp_common.c (506)]: > > > ajp_unmarshal_response: > > > Header[1] [Content-Language] = [en-US] > > > [Tue Jun 24 12:47:34 2003] [jk_isapi_plugin.c (428)]: Into > > > jk_ws_service_t::start_response > > > [Tue Jun 24 12:47:34 2003] [jk_ajp_common.c (698)]: received from > ajp13 > > > #756 > > > [Tue Jun 24 12:47:34 2003] [jk_isapi_plugin.c (562)]: Into > > > jk_ws_service_t::write > > > [Tue Jun 24 12:47:34 2003] [jk_ajp_common.c (698)]: received from > ajp13 > > > #2 > > > [Tue Jun 24 12:47:34 2003] [jk_isapi_plugin.c (872)]: > HttpExtensionProc > > > service() returned OK > > > [Tue Jun 24 12:47:34 2003] [jk_ajp_common.c (1307)]: Into > > > jk_endpoint_t::done > > > > > > I had assumed that it was the mapping to isapi_redirector.dll, that I > > > noted > > > in the first message, that was the problem. But I don't really know. > > > That's > > > why I'm looking for some guidance on what the log should be showing. > In > > > an > > > old log for a connection that worked there was not attempt to map > > > isapi_redirector.dll so I assume that part of the problem is there. I > > > just > > > can't figure out what would cause Tomcat to try to map the dll. > > > > > > This is the worker.properties. The only thing unusual is that I've > > > changed > > > localhost to the name of the server: inqtomcat. I've also changed it > back > > > to > > > localhost and it's not made any difference. > > > > > > Thanks for any more ideas. > > > > > > Ken > > > > > > > > > > > > # worker.ajp13.type=ajp13 # #Specifies the load balance factor when > used > > > with a load balancing worker. #Note: #-----> lbfactor must be > 0 > #-----> > > > Low lbfactor means less work done by the worker. # > > > worker.ajp13.lbfactor=1 # #Specify the size of the open connection > cache. > > > #worker.ajp13.cachesize # #------DEFAULT LOAD BALANCER WORKER > > > DEFINITION-- > > > > > > > > > > > > --------- # #The loadbalancer (type lb) worker perform weighted > round- > > > robin #load balancing with sticky sessions. #Note: #---> If a worker > > > dies, the load balancer will check its state once #in a while. Until > then > > > all work is redirected to peer worker. # worker.loadbalancer.type=lb > > > worker.loadbalancer.balanced_workers=ajp13 # #worker.tomcat_home > should > > > point to the location where you installed #tomcat. This is where you > have > > > your conf, webapps and lib directories. #Note: Please make sure to > enter > > > the appropriate path from your machine. # > > > worker.tomcat_home=C:\Tomcat4112 > > > # #worker.java_home should point to your Java installation. #Normally > you > > > should have a bin and lib directories beneath it. #Note: Please make > sure > > > to enter the appropriate path from your machine. # > > > worker.java_home=C:\java\jdk1.4 # #You should configure your > environment > > > slash...ps=\on NT and / on UNIX #and may be different elsewhere. # > ps=# > > > #- > > > > > > ------ADVANCED MODE------- #------------------------------ # # > #------- > > > DEFAULT worker list------ #---------------------------------- # #The > > > worker that your plugins should create and work with # > worker.list=ajp13 > > > # #----DEFAULT ajp13 WORKER DEFINITION----- # #Defining a worker > named > > > ajp13 and of type ajp13 #Note that the name and the type do not have > to > > > match. # worker.ajp13.port=8009 worker.ajp13.host=inqtomcat > > > #*****End worker.properties***** > > > > > > > > > > > > -----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, > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
