|Summary:||If the tomcat server cannot be resolved, apachectl configtest passes, but apachectl graceful fails|
|Product:||Tomcat Connectors||Reporter:||Chris <mchyzer>|
|Component:||mod_jk||Assignee:||Tomcat Developers Mailing List <dev>|
Description Chris 2009-11-24 12:28:20 UTC
We had a production issue where we added some servers, and configured them in workers.properties. However, some web servers didnt have the app servers in the /etc/hosts file. So the host names were not resolvable. We did an apachectl configtest and it passed. Then we did an apachectl graceful And apache died. We figured out the problem, but I think mod_jk should either: 1. Check for host resolution on a configtest -and/or- 2. Not fail to start if a host is not resolvable. Maybe throw an error, but dont kill apache. Here is the error we saw in mod_jk.log (note, the server name not resolvable is "pats") [Tue Nov 24 11:02:43 2009] [20247:3086329600] [error] ajp_validate::jk_ajp_common.c (2526): worker tomcat_a can't resolve tomcat address pats [Tue Nov 24 11:02:43 2009] [20247:3086329600] [error] wc_create_worker::jk_worker.c (163): validate failed for tomcat_a [Tue Nov 24 11:02:43 2009] [20247:3086329600] [error] build_worker_map::jk_worker.c (262): failed to create worker tomcat_a Thanks, Chris
Comment 1 Mladen Turk 2009-12-21 04:56:18 UTC
Fixed in the SVN. Since status worker now allows to change the contact address at runtime we can just disable the worker for which address resolution fails. The [ERROR] will be still logged however.
Comment 2 Rainer Jung 2010-02-23 02:53:28 UTC
Will be part of 1.2.29.