JBoss EAP 7 fails to connect to Apache httpd mod cluster due to a bad source port caused by |
您所在的位置:网站首页 › apache的httpd › JBoss EAP 7 fails to connect to Apache httpd mod cluster due to a bad source port caused by |
10/13/22, 10:38 PM JBoss EAP 7 fails to connect to Apache httpd/mod_cluster due to a bad source port caused by port-offset - Red Hat Custo... access.redhat/solutions/2840741 1/ Support cases will be inaccessible Oct. 16 12 am-12:20am ET for plannedmaintenance. To create cases during this time, use techsupport@redhat or if critical, call Red Hat. JBoss EAP 7 fails to connect to Apache httpd/mod_cluster due to a bad source port caused by port-off... Products & Services Knowledgebase JBoss EAP 7 fails to connect to Apachehttpd/mod_cluster due to a bad source portcaused by port-offset$ SOLUTION VERIFIED - Updated May 28 2020 at 10:53 PM - EnvironmentRed Hat JBoss Enterprise Application Platform (EAP) 7 mod_cluster IssueJBoss fails to connect to Apache httpd/mod_cluster due to permissions issues like the following: It starts successfully as root JBoss fails to connect to Apache httpd/mod_cluster due to "java.net: Cannot assign requested address (connect failed)" like the following: English ERROR [org.jboss] (UndertowEventHandlerAdapter - 1) MODCLUSTER000043: Failed to send INFO command to 127.0.0.1/127.0.0:6666: Permission denied (Bind failed) Subscriptions Downloads Containers Support Cases 10/13/22, 10:38 PM JBoss EAP 7 fails to connect to Apache httpd/mod_cluster due to a bad source port caused by port-offset - Red Hat Custo... access.redhat/solutions/2840741 2/ Product(s) Red Hat JBoss Enterprise Application Platform Component httpd jbossas Category Troubleshoot Tags apache eap jboss jboss_eap load_balancing mod_cluster I suspected ephemeral port exhaustion but I could not see such exhaustion from netstat output. ResolutionUpdate to EAP 7 CP 8 or later. Remove source-port="0" fixed-source-port="false" setting (the bad source-port setting) or give it a usable port number (greater than 1024 for non-root users): Root Causesetting for the mod_cluster proxy has source-port="0" fixed-source-port="false" setting but the port-offset feature changes the source port from ephermeral port to some bad port: This issue is reported in the following JIRAs: Upstream: [WFCORE-2026] source-port is wrongly offsetted when configured to 0, i. ephemeral port; results in "Permission denied (Bind failed)" - JBoss Issue Tracker EAP 7.1: [JBEAP-7433] Mod cluster not working with non-root user - JBoss Issue Tracker EAP 7.0: [JBEAP-12241] GSS Mod cluster not working with non-root user JBoss Issue TrackerERROR [org.jboss] (UndertowEventHandlerAdapter - 1) MODCLUSTER000043: Failed to send STATUS command to 127.0.0.1/127.0.0:6666: Cannot assign requested address
|
CopyRight 2018-2019 办公设备维修网 版权所有 豫ICP备15022753号-3 |