Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Not work:
BalancerMember ws://127.0.0.1 ping=1 connectiontimeout=3 route=1
Does work:
BalancerMember ws://127.0.0.1:80 ping=1 connectiontimeout=3 route=1
Version-Release number of selected component (if applicable):
httpd-2.4.6-80.el7.x86_64
How reproducible:
Steps to Reproduce:
1. install httpd and tomcat8
2. configure tomcat to use the port 80
# vim /etc/tomcat/server.xml
72 <Connector port="80" protocol="HTTP/1.1" address="0.0.0.0"
73 connectionTimeout="20000"
74 />
3. run tomcat as root
# /usr/lib/jvm/jre/bin/java -Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=9999 -Dcom.sun.m
anagement.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=true -Dcom.sun.management.jmxremote.registry.ssl=true -Djavax.
net.ssl.keyStorePassword=password -Djavax.net.ssl.keyStore=/etc/tomcat/keystore -classpath /usr/share/tomcat/bin/bootstrap.jar:/usr/shar
e/tomcat/bin/tomcat-juli.jar:/usr/share/java/commons-daemon.jar -Dcatalina.base=/usr/share/tomcat -Dcatalina.home=/usr/share/tomcat -Dja
va.endorsed.dirs= -Djava.io.tmpdir=/var/cache/tomcat/temp -Djava.util.logging.config.file=/usr/share/tomcat/conf/logging.properties -Dja
va.util.logging.manager=org.apache.juli.ClassLoaderLogManager org.apache.catalina.startup.Bootstrap start
4. configure httpd to use the port 81
Listen 81
5. copy the following proxy.conf to /etc/httpd/conf.d
LogLevel trace8
ProxyPass /examples/websocket/ balancer://clusterwss/examples/websocket/
ProxyPassReverse /examples/websocket/ balancer://clusterwss/examples/websocket/
ProxyPass / balancer://cluster/
ProxyPassReverse / balancer://cluster/
<Proxy balancer://cluster>
BalancerMember http://127.0.0.1 ping=1 connectiontimeout=3 route=1
</Proxy>
<Proxy balancer://clusterwss>
BalancerMember ws://127.0.0.1 ping=1 connectiontimeout=3 route=1
</Proxy>
6. start httpd
7. access http://localhost:81/examples/websocket/echo.xhtml
8. click programmatic API and the connect button
9. You will get the following error message:
[Thu Mar 15 17:10:22.796580 2018] [proxy:error] [pid 30466] (111)Connection refused: AH00957: WS: attempt to connect to 127.0.0.1:0 (127
.0.0.1) failed
10. change the proxy.conf which is created in the step 5 as follows(add :80)
<Proxy balancer://clusterwss>
BalancerMember ws://127.0.0.1:80 ping=1 connectiontimeout=3 route=1
</Proxy>
11. restart httpd
7. access http://localhost:81/examples/websocket/echo.xhtml
8. click programmatic API and the connect button, then you will see the websocket connection is establishded.
Actual results:
Expected results:
Additional info:
Comment 1Oneata Mircea Teodor
2018-03-15 10:13:40 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2018:3211
Description of problem: Not work: BalancerMember ws://127.0.0.1 ping=1 connectiontimeout=3 route=1 Does work: BalancerMember ws://127.0.0.1:80 ping=1 connectiontimeout=3 route=1 Version-Release number of selected component (if applicable): httpd-2.4.6-80.el7.x86_64 How reproducible: Steps to Reproduce: 1. install httpd and tomcat8 2. configure tomcat to use the port 80 # vim /etc/tomcat/server.xml 72 <Connector port="80" protocol="HTTP/1.1" address="0.0.0.0" 73 connectionTimeout="20000" 74 /> 3. run tomcat as root # /usr/lib/jvm/jre/bin/java -Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=9999 -Dcom.sun.m anagement.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=true -Dcom.sun.management.jmxremote.registry.ssl=true -Djavax. net.ssl.keyStorePassword=password -Djavax.net.ssl.keyStore=/etc/tomcat/keystore -classpath /usr/share/tomcat/bin/bootstrap.jar:/usr/shar e/tomcat/bin/tomcat-juli.jar:/usr/share/java/commons-daemon.jar -Dcatalina.base=/usr/share/tomcat -Dcatalina.home=/usr/share/tomcat -Dja va.endorsed.dirs= -Djava.io.tmpdir=/var/cache/tomcat/temp -Djava.util.logging.config.file=/usr/share/tomcat/conf/logging.properties -Dja va.util.logging.manager=org.apache.juli.ClassLoaderLogManager org.apache.catalina.startup.Bootstrap start 4. configure httpd to use the port 81 Listen 81 5. copy the following proxy.conf to /etc/httpd/conf.d LogLevel trace8 ProxyPass /examples/websocket/ balancer://clusterwss/examples/websocket/ ProxyPassReverse /examples/websocket/ balancer://clusterwss/examples/websocket/ ProxyPass / balancer://cluster/ ProxyPassReverse / balancer://cluster/ <Proxy balancer://cluster> BalancerMember http://127.0.0.1 ping=1 connectiontimeout=3 route=1 </Proxy> <Proxy balancer://clusterwss> BalancerMember ws://127.0.0.1 ping=1 connectiontimeout=3 route=1 </Proxy> 6. start httpd 7. access http://localhost:81/examples/websocket/echo.xhtml 8. click programmatic API and the connect button 9. You will get the following error message: [Thu Mar 15 17:10:22.796580 2018] [proxy:error] [pid 30466] (111)Connection refused: AH00957: WS: attempt to connect to 127.0.0.1:0 (127 .0.0.1) failed 10. change the proxy.conf which is created in the step 5 as follows(add :80) <Proxy balancer://clusterwss> BalancerMember ws://127.0.0.1:80 ping=1 connectiontimeout=3 route=1 </Proxy> 11. restart httpd 7. access http://localhost:81/examples/websocket/echo.xhtml 8. click programmatic API and the connect button, then you will see the websocket connection is establishded. Actual results: Expected results: Additional info: