to find out if IIS tries to contact tomcat at 8009. If you don't have one, I suggest Ethereal at
www.ethereal.com/
BTW: Do you get a strange stacktrace at startup (MBean something...)? Do the tomcat shutdown take a long time?
If so, you can try removing the connector at 8009 and instead use the 8081 one at port 8009.
The org.apache.coyote.tomcat4.CoyoteConnector is a new one used with jk2, but I can't imagine
that it won't work with jk as well, since the protocol is the same (ajp13).
Also you can add these rules to uriworkermap.properties, just to see if anything changes in the log file:
/localhost/mobilizer/mobilizer/*=$(default.worker) /mobilizer/mobilizer/*=$(default.worker)
Mats
Jon Skeet wrote:
<snip log>
It seems like /mobilizer/mobilizer/ finds its way through, but the path /localhost/mobilizer/mobilizer doesn't. Is that correct?What
is the path starting with /localhost, is this really your intention?
There shouldn't be any path starting with /localhost. I'm visiting the URL
http://localhost/mobilizer/mobilizer
but the localhost part is the servername, not the path.
This appears to be consistent with the log I get when I use the name of the computer rather than localhost, eg:
[Tue Sep 23 10:40:11 2003] [jk_uri_worker_map.c (351)]: Into jk_uri_worker_map_t::map_uri_to_worker [Tue Sep 23 10:40:11 2003] [jk_uri_worker_map.c (368)]: Attempting to map URI '/treebeard/mobilizer/mobilizer/' [Tue Sep 23 10:40:11 2003] [jk_uri_worker_map.c (456)]: jk_uri_worker_map_t::map_uri_to_worker, done without a match
My guess is that it's something IIS is doing for the sake of virtual hosting, but I wouldn't like to say for sure.
The /mobilizer/mobilizer path is the correct one - but I don't know why it's then not getting any further than it is doing.
Jon
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
