-
Bug
-
Resolution: Done
-
Critical
-
httpd 2.4.23 SP3 GA
-
None
-
16
-
-
-
-
-
-
+
WebSocket configuration for apache httpd (EnableWsTunnel) balancer enables only ws communication, but undertow as balancer enables both http and ws.
# 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/cache/mod_cluster ServerName dev89:2080 EnableWsTunnel LogLevel warn <IfModule manager_module> Listen 10.19.70.244:8747 <VirtualHost 10.19.70.244:8747> <Directory /> Require all granted </Directory> ServerAdvertise on EnableMCPMReceive <Location /mcm> SetHandler mod_cluster-manager Require all granted </Location> AdvertiseGroup 224.0.5.244:55918 AdvertiseBindAddress 10.19.70.244:55918 KeepAliveTimeout 60 MaxKeepAliveRequests 0 ServerAdvertise on AdvertiseFrequency 5 ManagerBalancerName qacluster </VirtualHost> </IfModule>
Worker joins with
<h1> Node jboss-eap-7.1 (ws://10.19.70.244:8080): </h1>
and all http comunication ends with
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>500 Internal Server Error</title> </head><body> <h1>Internal Server Error</h1> <p>The server encountered an internal error or misconfiguration and was unable to complete your request.</p> <p>Please contact the server administrator at Administrator@localhost to inform them of the time this error occurred, and the actions you performed just before this error.</p> <p>More information about this error may be available in the server error log.</p> <hr> <address>Apache/2.4.23 (Red Hat) Server at 10.19.70.244 Port 2080</address> </body></html>
And log message
[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 /clusterbench/jvmroute. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
- clones
-
MODCLUSTER-580 EnableWsTunnel enables only ws comunication
- Resolved
- is caused by
-
JBCS-291 jbcs httpd-2.4.23 as reverse proxy for backend websocket server using mod_proxy_wstunnel does not works
- Closed