Mod_Cluster Using Wrong IP Address For Lifecycle Events

Solution In Progress - Updated -

Issue

  • How do I change the IP address that mod_cluster (on JBoss) uses to send status pings and other lifecycle events to Httpd?

  • Although JBoss is bound to a specific IP address on the host, the mod_cluster listener is sending lifecycle events to Httpd via a different host IP address. JBoss is bound to IP 192.168.1.11:

INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTP listener default listening on 192.168.1.11:8080
INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow AJP listener ajp listening on 192.168.1.11:8009

The mod_cluster listener status pings are sent via a different address (192.168.1.13) on the same host (Httpd access logging):

192.168.1.13 - - [23/May/2023:17:34:47 -0400] "STATUS / HTTP/1.1" 200 59 "-" "ClusterListener/1.0"
192.168.1.13 - - [23/May/2023:17:34:57 -0400] "STATUS / HTTP/1.1" 200 59 "-" "ClusterListener/1.0"
192.168.1.13 - - [23/May/2023:17:35:07 -0400] "STATUS / HTTP/1.1" 200 59 "-" "ClusterListener/1.0"
192.168.1.13 - - [23/May/2023:17:35:17 -0400] "STATUS / HTTP/1.1" 200 59 "-" "ClusterListener/1.0"
192.168.1.13 - - [23/May/2023:17:35:27 -0400] "STATUS / HTTP/1.1" 200 59 "-" "ClusterListener/1.0"

Environment

Red Hat JBoss Enterprise Application Platform (EAP)

  • 7.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content