-
Type:
Feature Request
-
Status: Resolved (View Workflow)
-
Priority:
Blocker
-
Resolution: Done
-
Affects Version/s: 1.2.11.Final, 1.3.1.Final
-
Fix Version/s: 1.4.0.Alpha1, 2.0.0.Alpha1
-
Component/s: Core & Container Integration (Java)
-
Labels:
-
Git Pull Request:
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 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.
<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"
connector="http" advertiseGroupAddress="224.0.5.12" advertisePort="61217"
/>
Suggestion: Let's add the option to the catalina integration as well.
- cloned from
-
JWS-63 Tomcat mod_cluster integration does not allow one to choose a connector
-
- Verified
-
- is incorporated by
-
MODCLUSTER-531 Eliminate automagic
-
- Coding In Progress
-