Proxy Request Timeout Errors in Apache HTTPD with mod_cluster

Solution Verified - Updated -

Issue

  • Requests are failing because they are hitting a mod_cluster proxy timeout

    [Sun Jan 01 00:00:00.000000 1900] [proxy_ajp:error] [pid 99999] (70007)The timeout specified has expired: AH01030: ajp_ilink_receive() can't receive header
    [Sun Jan 01 00:00:00.000000 1900] [proxy_ajp:error] [pid 99999] [client <host>:<port>] AH00992: ajp_read_header: ajp_ilink_receive failed
    [Sun Jan 01 00:00:00.000000 1900] [proxy_ajp:error] [pid 99999] (70007)The timeout specified has expired: [client <host>:<port>] AH00878: read response failed from <server-host>:<server-port> ()
    
  • We use httpd and mod_cluster and see requests fail at times with 504s

  • The proxy requests are failing with the below error in Apache httpd error_log. When this message is logged, 504 Gateway Timeout will be returned to the client.
  • We have issue happening in the production environment for requests which take a longer processing time on the EAP server. The application makes calls to the other back-end systems and when these requests take a little longer to complete the EWS returns a Gateway timeout error.
  • The client request gets a Gateway Timeout error (HTTP 504) from JBoss EWS when accessed via the load balancer if the request takes a longer than usual, How to increase the timeout in EWS?
  • How can we increase this timeout?

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
  • Red Hat JBoss Web Server (JWS)
  • Red Hat JBoss Core Services (JBCS)
  • Apache Web Server (HTTPD)
    • mod_cluster

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content