Automatically handling deployment failures with mod_proxy

Solution Verified - Updated -


  • We use mod_proxy to balance load across several JBoss/Tomcat instances. If one instance has a deployment failure, mod_proxy continues to route requests to it, resulting 404s since the application is not successfully deployed. Is there anyway to get mod_proxy to recognize automatically that traffic should be sent to other instances instead of the 404/failed deployment instance?


  • JBoss Enterprise Application Platform
  • JBoss Enterprise Web Server
    • Apache httpd
      • mod_proxy
    • Tomcat

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