4 Replies Latest reply on Jan 5, 2011 3:10 AM by jfclere

How to handle context root collisions?

dbschofield Nov 4, 2010 11:05 AM

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?

1. Re: How to handle context root collisions?

pferraro Nov 17, 2010 10:55 AM (in response to dbschofield)

1. No - this is not the intended behavior.
2. Yes - this appears to be a bug. Can you file a jira?
Can you also verify that the contexts are correctly registered with the load balancer, i.e. are both contexts listed in mod_cluster-manager?
Actions
2. Re: How to handle context root collisions?

dbschofield Nov 22, 2010 9:38 AM (in response to pferraro)

I verified that both context roots are correctly showing up in mod_cluster-manager.
I have opened JIRA MODCLUSTER-196
Actions
3. Re: How to handle context root collisions?

jfclere Nov 25, 2010 5:29 AM (in response to dbschofield)

MODCLUSTER-196 is fixed now.
Actions
4. Re: How to handle context root collisions?

jfclere Jan 5, 2011 3:10 AM (in response to pferraro)

Probably MODCLUSTER-188
Actions

Go to original post