ROOT context is improperly enabled on mod_cluster when SSO is added to EAP 6

Solution Verified - Updated -


  • Using mod_cluster with EAP 6, we're seeing Apache static content and other requests that shouldn't be proxied to JBoss are proxied to JBoss regardless causing 404s and 503s
  • It looks like this started when SSO was added to our web subsystem as this caused the ROOT context to be improperly enabled on mod_cluster
  • We saw the ROOT context randomly enabled on one start up but it hasn't repeated on any other restarts.


  • JBoss Enterprise Application Platform (EAP) 6.x
  • mod_cluster 1.2.x

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