[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-242) requests routed to nodes where the context doesn't exist

[Michal Babacek (JIRA)]

     [ https://issues.jboss.org/browse/MODCLUSTER-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michal Babacek closed MODCLUSTER-242.
-------------------------------------



Closing. Clean-up.
At least one of the following applies:

  * the issue has been thoroughly tested as a part of one of the current releases
or
  * it hasn't occurred in ~2 years
or
  * it's utterly harmless

> requests routed to nodes where the context doesn't exist
> --------------------------------------------------------
>
>                 Key: MODCLUSTER-242
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-242
>             Project: mod_cluster
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.0.6
>            Reporter: Samuel Mendenhall
>            Assignee: Jean-Frederic Clere
>             Fix For: 1.0.8
>
>
> Env: 4 JBoss servers w/ mod_cluster sitting behind 2 Apache servers. The 2 Apache servers are proxying to the 4 JBoss servers. 
> Those 4 JBoss servers are split into 2 separate clusters, each cluster serving different applications. For example, Cluster1 has AppA and AppB, but Cluster2 has AppC and Appd. 
> When attempting to connect to any application through the Apache server, we randomly see 404 errors. Is this because Apache/mod_cluster is trying to route the request to all servers, instead of just the servers with the right web context enabled.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)