Problem with mod_jk 1.2 - 500 Internal Server Error
I'm using JBoss 4.0.1 with integrated Tomcat 5, and I'm trying to connect it to Apache 2. Whenever I make a request to a resource that should be passed along to Tomcat, I get a 500 Internal Server error. Looking at the mod_jk.log shows: [Thu Jan 13 13:45:34 2005] [jk_uri_worker_map.c (445)]: Into jk_uri_worker_map_t::map_uri_to_worker [Thu Jan 13 13:45:34 2005] [jk_uri_worker_map.c (459)]: Attempting to map URI '/status' [Thu Jan 13 13:45:34 2005] [jk_uri_worker_map.c (473)]: jk_uri_worker_map_t::map_uri_to_worker, Found an exact match default - /status [Thu Jan 13 13:45:34 2005] [mod_jk.c (1689)]: Into handler r-proxyreq=0 r-handler=jakarta-servlet r-notes=140779720 worker=default [Thu Jan 13 13:45:34 2005] [jk_worker.c (90)]: Into wc_get_worker_for_name default [Thu Jan 13 13:45:34 2005] [jk_worker.c (94)]: wc_get_worker_for_name, done did not find a worker [Thu Jan 13 13:45:34 2005] [jk_uri_worker_map.c (445)]: Into jk_uri_worker_map_t::map_uri_to_worker So it looks like it maps to the correct worker, but then can't find the worker. I've got no clue why this is happening. Here's my workers.properties file: # Define worker workers.list=default worker.default.port=8009 worker.default.host=localhost worker.default.type=ajp13 And here's the section of httpd.conf where it's all set up # # mod_jk settings # JkWorkersFile conf/workers.properties JkLogfile logs/mod_jk.log JkLogLevel debug JkMount /*.jsp default JkMount /*.do default JkMount /status default # End of mod_jk settings I'm really confused and frustrated with this...I'd appreciate any help. Thanks, Pat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with mod_jk 1.2 - 500 Internal Server Error
Pat Maddox wrote: I'm using JBoss 4.0.1 with integrated Tomcat 5, and I'm trying to connect it to Apache 2. Whenever I make a request to a resource that should be passed along to Tomcat, I get a 500 Internal Server error. Looking at the mod_jk.log shows: [Thu Jan 13 13:45:34 2005] [jk_worker.c (94)]: wc_get_worker_for_name, done did not find a worker # Define worker workers.list=default worker.default.port=8009 worker.default.host=localhost worker.default.type=ajp13 Can you resolve the 'localhost'? See if you have localhost inside etc/hosts or use 127.0.0.1 for host name. Also, you can provide the mod_jk version used (1.2.8, etc.) Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with mod_jk 1.2 - 500 Internal Server Error
Well, I managed to get it. And I feel unbelievably stupid (as is the case with most problems). The simple fix is worker.list=default rather than workers.list=default On Jan 13, 2005, at 11:03 AM, Mladen Turk wrote: Pat Maddox wrote: I'm using JBoss 4.0.1 with integrated Tomcat 5, and I'm trying to connect it to Apache 2. Whenever I make a request to a resource that should be passed along to Tomcat, I get a 500 Internal Server error. Looking at the mod_jk.log shows: [Thu Jan 13 13:45:34 2005] [jk_worker.c (94)]: wc_get_worker_for_name, done did not find a worker # Define worker workers.list=default worker.default.port=8009 worker.default.host=localhost worker.default.type=ajp13 Can you resolve the 'localhost'? See if you have localhost inside etc/hosts or use 127.0.0.1 for host name. Also, you can provide the mod_jk version used (1.2.8, etc.) Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
