Jeff, As far as I can tell, all requests (servlet or non-servlet) are being served properly.
I tried changing the log levels in the configuration. info - nothing is being logged at all as far as I can see. warn - tons of logging, including non-servlet items debug - same as warn with some more spcific detail. I'm starting to wonder if there might be a problem with my mod_jk.so. As I recall, it's from tomcat 3.3 which I compiled from source. (The AJP documentation said that 3.3 was the version to use.) Do you know which version of mod_jk.so you are using? Cindy At 02:11 PM 3/22/02 -0600, Jeff Larsen wrote: >I don't see anything in your setup that looks wrong. Just for kicks, I >set my test server's log level for mod_jk to "warn" and I didn't see >any messages relating to non-servlet document requests. Something is >fishy on your system. Are non-servlet requests being properly returned to >the browser? Your mod_jk log certainly makes it seem like '/images/logo_level2.gif' >is being mapped into the servlet name space. > >----- Original Message ----- >From: "Cindy Ballreich" <[EMAIL PROTECTED]> >To: "Tomcat Users List" <[EMAIL PROTECTED]> >Sent: Friday, March 22, 2002 1:46 PM >Subject: Re: REPOST: mod_jk.log question > > >> >> Thanks for your reply! >> >> Here is my mod_jk.conf which is referenced from httpd.conf... >> >> <IfModule !mod_jk.c> >> LoadModule jk_module libexec/mod_jk.so >> </IfModule> >> JkWorkersFile "/usr/local/java/catalina/conf/jk/workers.properties" >> JkLogFile "/usr/local/java/catalina/logs/mod_jk.log" >> JkLogLevel warn >> Alias /applications/ "/usr/local/java/catalina/webapps/applications" >> JkMount /applications/* ajp13 >> JkMount /applications/*.jsp ajp13 >> >> I do have an access log set up for Tomcat and it only shows requests for stuff >inside >the applications directory. It's ignoring anything requested from anywhere else. >Likewise, >Apache's access_log shows the request for the jsp page (which makes sense since it was >called on port 80), but nothing else. All this is as I would expect. >> >> However, mod_jk.log is showing an entry for every single request that comes to the >server, including Nimda probes!! I'm willing to ignore it if everything else is ok, >but >I'm concerned that I've got some sort of configuration error somewhere that's going to >bite me later on. >> >> Thanks again! >> >> Cindy >> >> >> At 12:25 PM 3/22/02 -0600, Jeff Larsen wrote: >> >It all depends on the relevant Alias and JkMount directives in your Apache >configuration. >> >You'll need to post them in order for us to make any useful analysis. Here's an >example >of >> >my config >> >where Apache serves the static content. The servlet context is "/online". >> > >> ># tell Apache where my app files are >> >Alias /online /www/tomcat/webapps/online >> > >> >JkMount /online/*.jsp ajp13 # Tomcat handles all JSP's >> ># mount only URL's SPECIFICALLY mapped to servlet, all >> ># others (like /online/images) are handled by Apache directly >> >JkMount /online/login ajp13 >> >JkMount /online/order ajp13 >> > >> >Also, look at the Tomcat access log (if you have one configured). Compare it to the >access >> >log >> >for Apache. If you have things set up right, you will see the static content >requests >in >> >the >> >Apache log, but not the Tomcat access log. >> > >> >Jeff >> > >> > >> >----- Original Message ----- >> >From: "Cindy Ballreich" <[EMAIL PROTECTED]> >> >To: <[EMAIL PROTECTED]> >> >Sent: Friday, March 22, 2002 11:04 AM >> >Subject: REPOST: mod_jk.log question >> > >> > >> >> >> >> I'm using mod_jk with Tomcat 4.0.1 and Apache 1.3.19 on a Redhat 7.0 system. >> >> >> >> Looking at my mod_jk.log file, it appears that mod_jk is trying to map every >request >> >that comes to my server, regardless of whether it should be handled by Tomcat or >Apache. >> >This seems very inefficient to me and I'm wondering if I have a configuration >problem >> >somewhere. Otherwise everything seems to be working correctly and all pages (jsp >and >> >otherwise) are being served correctly. Perhaps this is normal and I just need to >change >my >> >log level and ignore it. (log level is currently "warn".) I'd appreciate some >input. >> >> >> >> mod_jk.log entry of a request that should be (and is) handled by Apache... >> >> [Wed Mar 20 10:07:35 2002] [jk_uri_worker_map.c (351)]: Into >> >jk_uri_worker_map_t::map_uri_to_worker >> >> [Wed Mar 20 10:07:35 2002] [jk_uri_worker_map.c (368)]: Attempting to map URI >> >'/images/logo_level2.gif' >> >> [Wed Mar 20 10:07:35 2002] [jk_uri_worker_map.c (456)]: >> >jk_uri_worker_map_t::map_uri_to_worker, done without a match >> >> >> >> Thanks! >> >> >> >> Cindy >> >> >> >> >> >> >> >> -- >> >> To unsubscribe: <mailto:[EMAIL PROTECTED]> >> >> For additional commands: <mailto:[EMAIL PROTECTED]> >> >> Troubles with the list: <mailto:[EMAIL PROTECTED]> >> > >> > >> >-- >> >To unsubscribe: <mailto:[EMAIL PROTECTED]> >> >For additional commands: <mailto:[EMAIL PROTECTED]> >> >Troubles with the list: <mailto:[EMAIL PROTECTED]> >> > >> >> -- >> To unsubscribe: <mailto:[EMAIL PROTECTED]> >> For additional commands: <mailto:[EMAIL PROTECTED]> >> Troubles with the list: <mailto:[EMAIL PROTECTED]> > > >-- >To unsubscribe: <mailto:[EMAIL PROTECTED]> >For additional commands: <mailto:[EMAIL PROTECTED]> >Troubles with the list: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
