]
Radoslav Husar commented on MODCLUSTER-457:
-------------------------------------------
Just to note, the problem from the field is that since the connectors are chosen
automagically, people were forced to bump thread counts e.g. by 1, so that the connector
with higher thread count is chosen.
Expose Tomcat configuration to explicitly specify a connector to use
with the proxy
-----------------------------------------------------------------------------------
Key: MODCLUSTER-457
URL:
https://issues.jboss.org/browse/MODCLUSTER-457
Project: mod_cluster
Issue Type: Feature Request
Components: Core & Container Integration (Java)
Affects Versions: 1.2.11.Final, 1.3.1.Final
Reporter: Michal Karm Babacek
Assignee: Radoslav Husar
Priority: Blocker
Labels: ux
Configuring mod_cluster to leverage {{ws://}} with {{EnableWsTunnel}}
(mod_proxy_wstunnel) requires the Tomcat to use *http* instead of *ajp* connector.
Unlike
[
AS7/WildFly/EAP|https://github.com/wildfly/wildfly/blob/master/mod_cluste...]
mod_cluster integration, the Tomcat one ignores such option, i.e. there is nothing about
selecting a particular connector with a *connector* attribute in
[
mbeans-descriptors.xml|https://github.com/modcluster/mod_cluster/blob/b3a...].
<Listener
className="org.jboss.modcluster.container.catalina.standalone.ModClusterListener"
loadMetricClass="org.jboss.modcluster.load.metric.impl.BusyConnectorsLoadMetric"
loadMetricCapacity="1" loadHistory="9"
loadDecayFactor="2" stickySession="true"
stickySessionForce="false" stickySessionRemove="true"
advertise="true"
{color:red}*connector="http"*{color}
advertiseGroupAddress="224.0.5.12" advertisePort="61217"
/>
Suggestion: Let's add the option to the catalina integration as well.