Ok... some more information...
JkMount /*/servlet/* ajp13
It turns out, that this line breaks apache! Warning warning warning don't
use it! I just spent 5 hours recompiling apache, checking httpd.conf etc et
al to discover after a few hours sleep and a coffee that it's actually this
line in mod_jk.conf that's breaking my websites right now and not apache
being weird.
Now, to clarify a bit:
- I used to run tomcat 3.2.2, with the mod_jk that was released with it, and
the following line successfully mapped servlets to an ajp13 worker:
JkMount /servlet/* ajp13
- I now run tomcat 3.3.1, with the new mod_jk, and that line does not
successfully map servlets to an ajp13 worker. It fails, saying
"map_uri_to_worker, done without a match"
- the equivalent line for JSPs works fine for old tomcat & new tomcat - no
problems there.
- I tried adding /*/servlet/* ajp13 as a workaround - maybe the uri match
was failing because of the leading "webappname" i.e. the uri would look
like: "/testapp/servlet/index" . Initially, I had success - it was
successfully mapped to an ajp13 worker. However, it also mapped *everything*
else, regardless of how the path looked (html, directories, gifs, jpgs etc
etc etc) that lived in the normal apache htdocs directories. In other words,
tomcat had taken over apache! <insert growling tomcat noise here>
But, this still leaves me with the basic problem, which is that the stock
standard mod_jk.conf file isn't mapping servlets correctly.
So, some questions...
1. Is my mod_jk.conf file correct?
<IfModule mod_jk.c>
JkWorkersFile /usr/local/tomcat/conf/jk/workers.properties
JkLogFile /var/log/tomcat/jk.log
JkLogLevel error
JkMount /*.jsp ajp13
JkMount /servlet/* ajp13
</IfModule>
2. Is mod_jk behaving correctly?
3. If mod_jk isn't behaving correctly, how do I fix it / or get more
information from it?
Thanks,
Chris
|-----Original Message-----
|From: Larry Isaacs [mailto:[EMAIL PROTECTED]]
|Sent: Wednesday, 15 May 2002 00:24
|To: 'Tomcat Users List'
|Subject: RE: mod_jk not mapping uri successfully for servlets on 3.3.1
|
|
|The jakarta-tomcat-connectors/jk/native sources have small improvements
|and bug fixes over that found in jakarta-tomcat/src/native. One of the
|improvements is support for "JkMount /*/..." that you discovered.
|
|Cheers,
|Larry
|
|> -----Original Message-----
|> From: Chris Herrmann [mailto:[EMAIL PROTECTED]]
|> Sent: Wednesday, May 15, 2002 5:21 AM
|> To: [EMAIL PROTECTED]
|> Subject: RE: mod_jk not mapping uri successfully for
|servlets on 3.3.1
|>
|>
|> Hi Larry,
|>
|> No, I haven't tried:
|>
|> JkMount /testapp/servlet/* ajp13
|>
|> doing so now...
|>
|> I upgraded to the latest mod_jk.so as well from
|> jakarta.apache.org. I tried
|> both with and without eapi support to see if it made a
|difference (and
|> rebuilt apache with and without eapi support accordingly.
|> Currently it's
|> on).
|>
|> Ok... so... adding your suggestion above works...
|>
|> Previously, I haven't had to do this. I also tried adding:
|>
|> JkMount */servlet/* ajp13
|>
|> doesn't work but:
|>
|> JkMount /*/servlet/* ajp13
|>
|> does work.
|>
|> Has the way mod_jk parses paths changed in the latest version?
|>
|> Cheers,
|>
|> Chris
|>
|>
|> > Hi Chris,
|> >
|> > It is not clear if you tried:
|> >
|> > JkMount /testapp/servlet/* ajp13
|> >
|> > I assume you build the mod_jk.so from Tomcat 3.3.1's
|> source. Using a
|> > mod_jk from Tomcat 3.2.x has the potential to hang.
|> >
|> > Cheers,
|> > Larry
|>
|>
|>
|>
|> --
|> To unsubscribe, e-mail:
|> <mailto:tomcat-user-> [EMAIL PROTECTED]>
|> For
|> additional commands,
|> e-mail: <mailto:[EMAIL PROTECTED]>
|>
|
|--
|To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
