I'm having the same problem in EAP 7 and 7.2. Apache's mod_cluster does not register my jboss. The operating system is Red Hat Linux 7.6
Thanks in advance
Please, can anybody help me? There are no error traces and nothing. I don't understand why Apache does not see my jboss node.
FYI you post was marked as spam, thus it wasn't showing to anybody yet – approved it now.
Another thing is that the configuration of jboss eap 6.4.11 for the domain.xml does not work in eap 7.2.
Can you post what's the actual problem with the configuration? If you just boot the new domain with the old xml it will upgrade automatically to new schema versions – any chance you did that?. No need to change anything manually.
<mod-cluster-config advertise-socket="modcluster" proxy-list="IP:6666" proxy-url="/mod_cluster" advertise="true" connector="ajp">
You are using multicast discovery mechanism in conjunction with hard-coded proxy list – which one are you actually using?
Also, proxy-list is deprecated, use attribute 'proxies' which references outbound-socket-bindings, e.g.
/subsystem=modcluster/proxy=default:write-attribute(name=proxies, value=[proxy1, proxy2]
<proxy name="default" advertise-socket="modcluster" listener="ajp" proxy-list="IP:6666" proxy-url="/mod_cluster">
The subsystem now supports defining multiple configurations to register with multiple proxies or multiple hosts, thus the change.
I have tried even setting the mod_cluster using the EAP 7.2 console but no avail.
Can you post the error?
Where at the 6.4 installation I had a custom module.xml with all the dependencies and the following jars:
What do you need custom module.xml for?
Anyone can help me? I don't know if I need binaries to install there or what is happen?
The Apache is the same (with all mod_cluster libs), that registers the nodes in EAP 6.4
You do not need to upgrade your native binaries. The versions are compatible.
Thanks a lot for the answer. I have fixed now the issue. The problem was that I had a bad configuration for the server groups.
Now I'm seeing all instances at mod_cluster. I have 3 apache web servers with the mod_cluster modules and 3 jboss instances. I have server advertise explicity disabled but mod_cluster is discovering all the servers:
This is my configuration:
<proxy name="proxy1" advertise="false" advertise-socket="modcluster" listener="ajp" proxies="proxy1" proxy-url="/mod_cluster">
# 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
<VirtualHost 172.19.54.11:16666> # change IP address to suit your environment
# KeepAliveTimeout 300
# MaxKeepAliveRequests 0
# AdvertiseSecurityKey secret # change key to match jboss config below
Require ip list_of_ips
Thanks a lot for the help
1 of 1 people found this helpful
Remember that this is a discovery mechanism, once a node is discovered, just because you disabled advertising where the server is, since its already discovered the WildFly instances are already aware of it. You can just restart the wildfly servers or use a management operation to remove those discovered proxies.
Thanks a lot for the answer.
I have managed to fix the problem. Restarting the servers made not effect, but cleaning tmp and data directories worked and now mod_cluster is registering the instances properly. Seems like a bug
Just to confirm, did you restart the load balancers or the backend workers?