https://bz.apache.org/bugzilla/show_bug.cgi?id=62799
Bug ID: 62799
Summary: mod_jk doesn't handle the EINPROGRESS state
appropriately for non-blocking sockets.
Product: Tomcat Connectors
Version: 1.2.42
Hardware: All
OS: Linux
Status: NEW
Severity: major
Priority: P2
Component: mod_jk
Assignee: dev@tomcat.apache.org
Reporter: m...@blackmans.org
Target Milestone: ---
We can see that when we use non-blocking sockets as result of the event MPM in
Apache 2.4, a value of 5 seconds for the connect_socket_timeout results in
connection errors due to EINPROGRESS (115) errors like so:
[Mon Sep 24 10:58:25.282 2018] [3334428:140116430018304] [info]
jk_open_socket::jk_connect.c (817): connect to 10.212.32.20:10153 failed
(errno=115)
[Mon Sep 24 10:58:25.283 2018] [3334428:140116430018304] [info]
ajp_connect_to_endpoint::jk_ajp_common.c (1068): (dw15716_rtc_0) Failed opening
socket to (10.212.32.20:10153) (errno=115)
[Mon Sep 24 10:58:25.283 2018] [3334428:140116430018304] [error]
ajp_send_request::jk_ajp_common.c (1728): (dw15716_rtc_0) connecting to backend
failed. Tomcat is probably not started or is listening on the wrong port
(errno=115)
[Mon Sep 24 10:58:25.283 2018] [3334428:140116430018304] [info]
ajp_service::jk_ajp_common.c (2778): (dw15716_rtc_0) sending request to tomcat
failed (recoverable), because of error during request sending (attempt=3)
EINPROGRESS should not be a failing error state. I assume values other than 5
seconds would have the same outcome.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
