[JBoss JIRA] (MODCLUSTER-168) mod_cluster should use hostname provided in address instead a IP address
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-168?page=com.atlassian.jira.pl... ]
Radoslav Husar updated MODCLUSTER-168:
--------------------------------------
Fix Version/s: 1.3.1.Beta2
(was: 1.3.1.Beta1)
> mod_cluster should use hostname provided in address instead a IP address
> ------------------------------------------------------------------------
>
> Key: MODCLUSTER-168
> URL: https://issues.jboss.org/browse/MODCLUSTER-168
> Project: mod_cluster
> Issue Type: Feature Request
> Affects Versions: 1.1.0.CR3
> Environment: any
> Reporter: Jean-Frederic Clere
> Assignee: Radoslav Husar
> Fix For: 1.2.11.Final, 1.3.1.Beta2
>
>
> The CONFIG message contains something like:
> JVMRoute=51ec121e-2976-3d75-bfd9-9e662bbb4bcd&Host=10.33.144.3&Port=8009&Type=ajp
> Even if the Connector is defined like:
> <Connector port="8009" address= "jfcpc" protocol="AJP/1.3" redirectPort="8443" />
> There are 2 ways to fix:
> - Use the String (Change the Connector.java in mod_cluster).
> - Use parameters.put("Host", connector.getAddress().getHostName()); when building the CONFIG message.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (MODCLUSTER-391) mod_cluster and mod_proxy integration
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-391?page=com.atlassian.jira.pl... ]
Radoslav Husar updated MODCLUSTER-391:
--------------------------------------
Fix Version/s: 1.3.1.Beta2
(was: 1.3.1.Beta1)
> mod_cluster and mod_proxy integration
> -------------------------------------
>
> Key: MODCLUSTER-391
> URL: https://issues.jboss.org/browse/MODCLUSTER-391
> Project: mod_cluster
> Issue Type: Bug
> 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.2.11.Final, 1.3.1.Beta2
>
> 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)|
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years