4 Replies Latest reply on Jan 5, 2011 3:10 AM by Jean-Frederic Clere

    How to handle context root collisions?

    Ben Schofield Novice

      I have a JBoss farm running JBoss EAP 5.0.1 with mod_cluster 1.1.0 GA.

      JBoss instance A hosts application A which has a context root of /abc.

      JBoss instance B hosts application B which has a context root of /abc/xyz


      The behavior I see is that requests meant for application B are getting routed to application A on JBoss instance A and the result is an http error 404.  Experience with other http load balancers tells me the more specific context root should be prefered.  For example a request to /abc/xyz/my.jsp would correctly go to application B on JBoss instance B.


      So my questions are:

      1) Is the current behavior for mod_cluster the intended behavior and if so what is the reasoning behind it?  Can this behavior be changed in anyway?

      2) Is this a bug and should I open a JIRA?