1 of 1 people found this helpful
I think what is shown in youtube video also works with a domain configuration. One server-group needs to get the load-balancer profile and load-balancer sockets in domain.xml. And the server in that group in host.xml needs to have auto-start=true so the loadbalancer starts. And for the profiles you need to do the same what is shown in the video. Config modcluster, security-key, ports, etc.
Thanks Erik , I will try this and update back here.
Hi Erik Thanks! it worked I followed the steps mentioned in youtube link.
I'm trying to do the same thing but I'm stuck.
For now, i've successfuly created a cluster on three VMs with a master and two slaves in domain mode.
Everything works fine except for the load balancer.
I didn't found updated docs to get the job done, tried some stuff but nothing worked.
This is the topology:
(IPs, naming and all stuff are a mess, it's just a first approach)
Apps and persistence units are deployed and configured on master and replicated to slaves by the master, and context is accesible on all servers.
But if I try to get the context on port 80 (load balancer), all I got is a 404. Also, it doesn't show the "welcome to WildFly" startup page for no-context requests.
loadbalancer-host throws this warn on startup:
No routing provider found for default-server; using legacy provider based on static configuration