Connection reset by peer: ajp_ilink_receive() can’t receive header

ajpliferaymod-proxy-ajp

I am seeing this in Liferay 6 (a Tomcat-based clustered webapp)'s log:

APR does not understand this error code: proxy: read response failed from [::1]:8009 (localhost)
The timeout specified has expired: ajp_ilink_receive() can't receive header
ajp_read_header: ajp_ilink_receive failed

[... the 3 lines above repeated many times ...]

Connection reset by peer: ajp_ilink_receive() can't receive header
APR does not understand this error code: proxy: read response failed from (null) (localhost)
ajp_read_header: ajp_ilink_receive failed

[... the 3 lines above repeated many times ...]

The webapp becomes unusable (the web UI does not respond to web requests) when the "Connection reset by peer" errors start appearing.

While the first problem (The timeout specified has expired) is covered by another question, what usually causes the second problem (Connection reset by peer), and what is the difference between the two problems?

Best Answer

Based on this question being asked by others on different websites, I will suggest you set the connection timeout.

Example is below.

ProxyPass / ajp://localhost:8009/ timeout=600

https://stackoverflow.com/questions/32093534/ah01030-ajp-ilink-receive-cant-receive-header

mod_proxy_ajp (70007)The timeout specified has expired: ajp_ilink_receive() can't receive header

If you already have a connection timeout specified in the configuration, another user found if they changed mod_proxy_ajp to mod_jk.

https://community.atlassian.com/t5/Jira-questions/503-Error-ajp-read-header-ajp-ilink-receive-failed/qaq-p/130248

Related Topic