+++ This bug was initially created as a clone of Bug #1328231 +++ 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
ASF 56452 was fixed in 1.2.40 ASF 59164 is still new but the fix looks "easy".
@Jan Stefl: Consider: https://bugzilla.redhat.com/show_bug.cgi?id=1328231#c12
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
The issues is not fixed, after described configuration I get: > [notice] child pid 19865 exit signal Segmentation fault (11) Verification FAILED, returning to ASSIGNED.
@Jan Stefl, could you talk to Jan Onderka about it? He has never managed to reproduce the issue: https://bugzilla.redhat.com/show_bug.cgi?id=1328231
@Michal Babacek, yes we have talked about it already. Just for complete the information: Problem is in EAP native-web-connectors (for EAP 6.4.10) and EWS-2.1.1 as well.