mod_proxy_http always hits POST ping timeout with EAP 7

Solution Verified - Updated -

Issue

  • Slower POST requests are hitting mod_proxy_http's ping timeout waiting for a 100-continue responses:
[proxy_http:error] [pid 11748] (70007)The timeout specified has expired: [client 127.0.0.1:34454] AH01102: error reading status line from remote server localhost:8080
[proxy:error] [pid 11748] [client 127.0.0.1:34454] AH00898: Timeout on 100-Continue returned by /app/
  • It looks like EAP 7 never sends a 100-continue response. This was not experienced previously with EAP 6.

Environment

  • JBoss Enterprise Application Platform (EAP)
    • 7.0.x
    • 7.1.0
  • JBoss Core Services (JBCS) httpd
    • 2.4.23 SP3
      • mod_proxy_http
      • mod_cluster

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.