How to configure Mod_cluster to return 500 in stead of 404 when JBoss not up?

Solution Verified - Updated -

Issue

We use a Apache - modcluster - JBoss setup. We saw that we get a different http error code when the JBoss workers are in error state (503 service temporarily not available) versus when JBoss is stopped normally (404 page not found), as the JBoss proxypass is not available and Apache tries to find the the JBoss page in its document root.
Is there a possibility to have Apache return the same error code?

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
  • Apache httpd
  • 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