Bug 55781 - ajp_read_header: ajp_ilink_receive failed; 120006)APR does not understand this error code: proxy: read response failed from x.x.x.x:xxxx
Summary: ajp_read_header: ajp_ilink_receive failed; 120006)APR does not understand thi...
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_proxy_ajp (show other bugs)
Version: 2.2.3
Hardware: Other Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2013-11-15 11:48 UTC by Joji Johny
Modified: 2018-11-07 21:09 UTC (History)
1 user (show)


Note You need to log in before you can comment on or make changes to this bug.
Description Joji Johny 2013-11-15 11:48:26 UTC
Since a month now, I have been seeing the following error messages in my httpd servers:
[Mon --- ---------- ----] [error] ajp_read_header: ajp_ilink_receive failed
[Mon --- ---------- ----] [error] (120006)APR does not understand this error code: proxy: read response failed from (localhost)

I have tried varies timeout settings that have been mentioned on various other websites, however the issue does not get resolved.

This application has high traffic through out the day 24/7.

Some users also report that they get the HTML source version of the page when accessing certain URL's and the above log message is what I get in the logs.

Please look into the same.

Joji Johny
Comment 1 Nihil 2015-10-22 11:09:34 UTC
Did you get any root cause and resolution?
Comment 2 William A. Rowe Jr. 2018-11-07 21:09:42 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.