snip > > workers.list=ajp13 > > workers.ajp13.port=8009 > > workers.ajp13.host=correct.server.name > > workers.ajp13.type=ajp13 > > > > apache = 1.3.27 > > jakarta = 4.0.6 > > This is different from what you had previously. So what is/isn't > happening now, and what (error) messages are you seeing in the logs?
mod_jk.log [Tue Oct 15 15:07:59 2002] [jk_uri_worker_map.c (502)]: jk_uri_worker_map_t::map_uri_to_worker, Found a context match ajp13 - > /examples/servlet/ [Tue Oct 15 15:07:59 2002] [jk_worker.c (132)]: Into wc_get_worker_for_name ajp13 [Tue Oct 15 15:07:59 2002] [jk_worker.c (136)]: wc_get_worker_for_name, done did not found a worker error log nothing! access log 192.168.43.222 - - [15/Oct/2002:15:07:59 -0400] "GET /examples/servlet/CookieExample HTTP/1.1" 500 608 To my feeble brain, this sounds like apache is trying to render the page, instead of forwarding to tomcat, so I get the 500. Tomcat SHOULD be able to handle the request (netstat confirms I still have an 09 listener). The only other thing I can think of, is I dl'ed the source for mod_jk and built it myself, and I see that it declares itself a beta for the version I dl'ed (mod_jk/1.2.1-beta-1). Are there any known issues with this mod_jk? --- Aryeh Katz VASCO www.vasco.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
