https://bz.apache.org/bugzilla/show_bug.cgi?id=63859
--- Comment #27 from JasonDo <afu000...@gmail.com> --- Dear all, In our production environment, we did see mod_jk log print log. Fri Mar 05 10:00:14.906 2021] [17221:139662211758208] [info] ajp_handle_cping_cpong::jk_ajp_common.c (979): (worker3) timeout in reply cpong after 10000 ms. Socket = 13 (event=110) [Fri Mar 05 10:00:14.951 2021] [27663:139662211758208] [info] ajp_handle_cping_cpong::jk_ajp_common.c (979): (worker3) timeout in reply cpong after 10000 ms. Socket = 13 (event=110) [Fri Mar 05 10:00:14.971 2021] [3615:139662211758208] [error] uri_worker_map_update::jk_uri_worker_map.c (1320): Unable to stat the /etc/httpd/conf/uriworkermap.properties (errno=13) [Fri Mar 05 10:00:14.990 2021] [3617:139662211758208] [error] uri_worker_map_update::jk_uri_worker_map.c (1320): Unable to stat the /etc/httpd/conf/uriworkermap.properties (errno=13) [Fri Mar 05 10:00:14.996 2021] [3616:139662211758208] [error] uri_worker_map_update::jk_uri_worker_map.c (1320): Unable to stat the /etc/httpd/conf/uriworkermap.properties (errno=13) [Fri Mar 05 10:00:15.006 2021] [17221:139662211758208] [info] ajp_send_request::jk_ajp_common.c (1654): (worker3) failed sending request, socket -1 prepost cping/cpong failure (errno=110) [Fri Mar 05 10:00:15.006 2021] [17221:139662211758208] [info] ajp_send_request::jk_ajp_common.c (1712): (worker3) no usable connection found, will create a new one, detected by connect check (0), cping (1), send (0). [Fri Mar 05 10:00:15.026 2021] [16683:139662211758208] [info] ajp_handle_cping_cpong::jk_ajp_common.c (979): (worker3) timeout in reply cpong after 10000 ms. Socket = 15 (event=110) [Fri Mar 05 10:00:15.051 2021] [27663:139662211758208] [info] ajp_send_request::jk_ajp_common.c (1654): (worker3) failed sending request, socket -1 prepost cping/cpong failure (errno=110) [Fri Mar 05 10:00:15.051 2021] [27663:139662211758208] [info] ajp_send_request::jk_ajp_common.c (1712): (worker3) no usable connection found, will create a new one, detected by connect check (0), cping (1), send (0). [Fri Mar 05 10:00:15.126 2021] [16683:139662211758208] [info] ajp_send_request::jk_ajp_common.c (1654): (worker3) failed sending request, socket -1 prepost cping/cpong failure (errno=110) [Fri Mar 05 10:00:15.126 2021] [16683:139662211758208] [info] ajp_send_request::jk_ajp_common.c (1712): (worker3) no usable connection found, will create a new one, detected by connect check (0), cping (1), send (0). [Fri Mar 05 10:00:15.667 2021] [18182:139662211758208] [info] ajp_handle_cping_cpong::jk_ajp_common.c (979): (worker3) timeout in reply cpong after 10000 ms. Socket = 13 (event=110) the configuration is as below: /etc/httpd/conf/workers.properties #Set properties for template worker.template.type=ajp13 worker.template.host=localhost worker.template.ping_timeout=10000 worker.template.ping_mode=A from the tomcat official doc - https://tomcat.apache.org/tomcat-8.5-doc/changelog.html this bug has been fixed in Tomcat 8.5.48 (markt) 63859: Do not perform a blocking read after a CPING message is received by the AJP connector because, if the JK Connector is configured with ping_mode="I", the CPING message will not always be followed by the start of a request. (markt) my tomcat version is 8.5.55. it should be fixed already in 8.5.55. When we see this error log, does it means this issue was not completely fixed in some case, or maybe, because the tomcat server is too busy, and did not respond timely? it impacts production stability, is it making sense to change the ping_mode=A to ping_mode=C to eliminate this issue? Given we cannot reproduce the issue in the lab, not sure if it is good to change to ping_mode=C, if change to ping_mode=c, is there any possible negative impact? any feedback would be much appreciated? -- 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
