mod_cluster and mod_proxy integration ------------------------------------- Key: MODCLUSTER-391 URL: https://issues.jboss.org/browse/MODCLUSTER-391 Project: mod_cluster Issue Type: Bug Security Level: Public(Everyone can see) Affects Versions: 1.2.6.Final Environment: All platforms we build mod_cluster for. Reporter: Michal Babacek Assignee: Jean-Frederic Clere Labels: native_libraries Fix For: 1.3.1.Final, 1.2.10.Final Attachments: error_log, mod_cluster.conf, mod_proxy.conf, standalone-ha.xml This Jira encapsulates all concerns regarding mod_cluster - mod_proxy integration. For instance, while basic {{ProxyPass}} settings work just fine, e.g. serving some files on {{/static}} from the Apache HTTP itself: {code} ProxyPassMatch ^/static/ ! ProxyPass / balancer://qacluster stickysession=JSESSIONID|jsessionid nofailover=on ProxyPassReverse / balancer://qacluster ProxyPreserveHost on {code} there are more complex setups, involving {{BalancerMember}} configurations, that do not work as expected. In the following example, one wanted to have {{/clusterbench}} application managed by mod_cluster, dynamically, while at the same time, in a different VirtualHost, having {{/tses}} application handled by manually created mod_proxy balancer settings. Attached [^mod_cluster.conf], [^mod_proxy.conf], [^standalone-ha.xml](modcluster subsystem element only) and [^error_log]. The aforementioned setup resulted in: |HTTP 200|(From worker)|http://10.16.88.19:8847/clusterbench/requestinfo/|OK|(/)| |HTTP 404|(From httpd)|http://10.16.88.19:8847/tses/session.jsp|Expected fail|(/)| |HTTP 503|(From httpd)|http://10.16.88.19:2182/tses/session.jsp|Unexpected fail|(x)|