From issues at jboss.org Mon Mar 23 12:58:02 2020 Content-Type: multipart/mixed; boundary="===============2124201301946503954==" MIME-Version: 1.0 From: Jean-Frederic Clere (Jira) To: mod_cluster-issues at lists.jboss.org Subject: [mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-580) EnableWsTunnel enables only ws comunication Date: Mon, 23 Mar 2020 12:58:04 -0400 Message-ID: In-Reply-To: JIRA.12687204.1491908823000@Atlassian.JIRA --===============2124201301946503954== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ https://issues.redhat.com/browse/MODCLUSTER-580?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13718= 936#comment-13718936 ] = Jean-Frederic Clere edited comment on MODCLUSTER-580 at 3/23/20 12:56 PM: -------------------------------------------------------------------------- https://httpd.apache.org/docs/2.4/mod/mod_proxy.html#proxypass look for upg= rade. Use: WSUpgradeHeader like the upgrade=3D in proxypass. Note that WSUpgradeH= eader applies to all VirtualHost/Balancer. was (Author: jfclere): https://httpd.apache.org/docs/2.4/mod/mod_proxy.html#proxypass look for upg= rade. > EnableWsTunnel enables only ws comunication > ------------------------------------------- > > Key: MODCLUSTER-580 > URL: https://issues.redhat.com/browse/MODCLUSTER-580 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.5.Final > Reporter: Bogdan Sikora > Assignee: Jean-Frederic Clere > Priority: Major > > WebSocket configuration for apache httpd (EnableWsTunnel) balancer enable= s only ws communication, but undertow as balancer enables both http and ws. = > {noformat} > # mod_proxy_balancer should be disabled when mod_cluster is used > LoadModule proxy_cluster_module modules/mod_proxy_cluster.so > LoadModule cluster_slotmem_module modules/mod_cluster_slotmem.so > LoadModule manager_module modules/mod_manager.so > LoadModule advertise_module modules/mod_advertise.so > MemManagerFile /mnt/hudson_workspace/mod_cluster/jbcs-httpd24-2.4/httpd/c= ache/mod_cluster > ServerName dev89:2080 > EnableWsTunnel = > LogLevel warn > > Listen 10.19.70.244:8747 > > > Require all granted > > ServerAdvertise on > EnableMCPMReceive > > SetHandler mod_cluster-manager > Require all granted > > AdvertiseGroup 224.0.5.244:55918 > AdvertiseBindAddress 10.19.70.244:55918 > KeepAliveTimeout 60 > MaxKeepAliveRequests 0 > ServerAdvertise on > AdvertiseFrequency 5 > ManagerBalancerName qacluster > > = > {noformat} > Worker joins with = > {noformat} >

Node jboss-eap-7.1 (ws://10.19.70.244:8080):

> {noformat} > and all http comunication ends with = > {noformat} > > > 500 Internal Server Error > >

Internal Server Error

The server encountered an internal error or > misconfiguration and was unable to complete > your request.

Please contact the server administrator at = > Administrator(a)localhost to inform them of the time this error occurred, > and the actions you performed just before this error.

More information about this error may be available > in the server error log.

Apache/2.4.23 (Red Hat) Server at 10.19.70.244 Port 2080 > > {noformat} > And log message = > {noformat} > [Sat Apr 08 16:21:29.335633 2017] [proxy:warn] [pid 12680] [client 10.19.= 70.244:55922] AH01144: No protocol handler was valid for the URL /clusterbe= nch/jvmroute. If you are using a DSO version of mod_proxy, make sure the pr= oxy submodules are included in the configuration using LoadModule. > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008) --===============2124201301946503954==--