Uploaded image for project: 'mod_cluster'
  1. mod_cluster
  2. MODCLUSTER-391

mod_cluster and mod_proxy integration

    XMLWordPrintable

Details

    Description

      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:

      ProxyPassMatch ^/static/ !
ProxyPass / balancer://qacluster stickysession=JSESSIONID|jsessionid nofailover=on
ProxyPassReverse / balancer://qacluster
ProxyPreserveHost on

      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

      Attachments

        1. standalone-ha.xml
          0.4 kB
        2. mod_proxy.conf
          0.7 kB
        3. mod_cluster.conf
          1 kB
        4. error_log
          94 kB

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. MODCLUSTER-543 BalancerMember directives don't work and cause SegFaults

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. MODCLUSTER-356 BalancerMember directives cause httpd crash when using mod_cluster 1.2.x

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Feature Request - Feature requests from customers and/or users MODCLUSTER-343 mod_cluster shouldn't overwrite stickysession=XXX|xxx from ProxyPass directives...

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Bug - A problem that impairs or prevents the functions of the product. MODCLUSTER-274 ProxyPass doesn't work with mod_cluster whne mixing mod_cluster and other scheme handlers

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. MODCLUSTER-305 ProxyPass can break StickySession

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. MODCLUSTER-397 StickySessions don't work for ProxyPass from unenabled context

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. MODCLUSTER-430 CreateBalancers behave the same with option 0 or 2

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. JBCS-375 mod_cluster + mod_proxy_wstunnel causes Segmentation Fault

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBCS-854 mod_cluster + mod_proxy_wstunnel doesn't work - all workers are in an error state

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. MODCLUSTER-364 mod_cluster and mod_proxy : keeping session

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. MODCLUSTER-425 The timeout specified has expired: proxy: AJP: cping/cpong failed,ajp_ilink_receive() can't receive header

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. MODCLUSTER-351 500 error when using ProxyPassReverse and proxying RewriteRule to the balancer

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Open

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) MODCLUSTER-390 add failonstatus to mod_cluster

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Activity

            People

              rhn-engineering-jclere Jean-Frederic Clere
              mbabacek1@redhat.com Michal Karm
              Michal Karm Michal Karm
              Votes:
              2 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: