Description of problem: Segfault occurrs in mod_jk when trying to resolve an unknown hostname. Version-Release number of selected component (if applicable): mod_jk-ap22 How reproducible: Always Steps to Reproduce: 1. Configure mod_jk 2. In workers.properties, set worker host to something that will not be resolved: 3. Make request: curl http://localhost/fail Here's a simple reproducing config: JkMount /* worker1 worker.list=worker1 worker.worker1.type=ajp13 worker.worker1.host=testhost # ping testhost ping: unknown host testhost Actual results: Segmentation fault Expected results: Nice error message about not being able to resolve hostname Additional info: Related upstream reports: https://bz.apache.org/bugzilla/show_bug.cgi?id=56452 https://bz.apache.org/bugzilla/show_bug.cgi?id=59164 https://mail-archives.apache.org/mod_mbox/tomcat-dev/201501.mbox/%3C20150101213422.B7310AC08A8@hades.apache.org%3E
per mod_jk update.
Created attachment 1171511 [details] worker.properties
Created attachment 1171513 [details] error_log
Created attachment 1171514 [details] workers.properties
Created attachment 1171518 [details] mod_jk.conf
Hello, I was trying to reproduce this issue, but seqFault never occurs. Can anybody provide any additional information about it? I always got error like "[Thu Jun 23 14:27:11 2016][2296:140440171694048] [error] ajp_validate::jk_ajp_common.c (2748): worker worker1 can't resolve tomcat address testhost" It was tested at versions EWS 2.0.0, 2.1.0 and JWS 3.0.0. Also I upload files which were used as configs, see attachment.
(In reply to Jan Onderka from comment #6) > Hello, > > I was trying to reproduce this issue, but seqFault never occurs. Can anybody > provide any additional information about it? I always got error like "[Thu > Jun 23 14:27:11 2016][2296:140440171694048] [error] > ajp_validate::jk_ajp_common.c (2748): worker worker1 can't resolve tomcat > address testhost" > It was tested at versions EWS 2.0.0, 2.1.0 and JWS 3.0.0. Also I upload > files which were used as configs, see attachment. Tested with mod_jk/1.2.36, mod_jk/1.2.40
(In reply to Jean-frederic Clere from comment #1) > per mod_jk update. Can you be more specific, please?
See rhbz 1342071
Actual the update to 1.2.41 fixes the ASFBZ 56452 so the issue should be fixed by the update.
This issue has been resolved in mod_jk-1.2.42 per a similar upstream report. Is the upstream report same as this bugzilla? https://bz.apache.org/bugzilla/show_bug.cgi?id=59164
Actually the svn commit: r1760598 isn't in our code so the bug is still there. Please reopen (and create the corresponding JBCS issue is it isn't forgotten)
@Jan Onderka, Jan Stefl can reproduce the issue: https://bugzilla.redhat.com/show_bug.cgi?id=1338661#c4