[mod_cluster-issues] [JBoss JIRA] Updated: (MODCLUSTER-242) requests routed to nodes where the context doesn't exist
Jean-Frederic Clere (JIRA)
jira-events at lists.jboss.org
Sat Jun 18 12:32:23 EDT 2011
[ https://issues.jboss.org/browse/MODCLUSTER-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Frederic Clere updated MODCLUSTER-242:
-------------------------------------------
Affects Version/s: 1.0.6
(was: 1.0.10)
> 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
> Affects Versions: 1.0.6
> Reporter: Samuel Mendenhall
> Assignee: Jean-Frederic Clere
> Fix For: 1.0.11
>
>
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the mod_cluster-issues
mailing list