503 errors when using mod_jk connecting to EAP due to errno=115

Solution Verified - Updated -

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
  • Red Hat JBoss Enterprise Web Server (EWS)
    • Apache httpd

Issue

  • Requests occasionally fail with a 503 error due to errno 115:
[Wed Oct 08 11:04:31 2014][9023:140345706768128] [error] ajp_service::jk_ajp_common.c (2643): (cluster02_1) connecting to tomcat failed.
[Wed Oct 08 11:04:33 2014][9023:140345706768128] [error] ajp_send_request::jk_ajp_common.c (1630): (cluster01_1) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=115)

Resolution

  • Remove socket_timeout and socket_connect_timeout from your workers.properties

Root Cause

  • A failure occurred handling the non-blocking EINPROGRESS used with these timeouts

Diagnostic Steps

  • Check the server.log for any reason why the EAP instances might have been unavailable during the period.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments