-
1. Re: Can registration by done by clients? Avoid multicast discovery?
mbabacek May 2, 2016 2:39 PM (in response to bill.burke)Yes, add outbound socket binding:
/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=my-proxies:add(host=10.10.10.11,port=3333)
and then add this proxy of yours to mod_cluster subsystem config:
/subsystem=modcluster/mod-cluster-config=configuration:write-attribute(name=proxies, value="my-proxies")
(written from the top of my head, complimentary typos could be included )
-
2. Re: Can registration by done by clients? Avoid multicast discovery?
bill.burke May 2, 2016 5:20 PM (in response to mbabacek)I just can't get this to work. How can you turn off all the multicast stuff? What values do you put in the outbound-socket-binding? What host/port is the load balancer listening for connection messages? How do you set that host/port? What is the "management-socking-binding"?
-
3. Re: Can registration by done by clients? Avoid multicast discovery?
rhusar May 10, 2016 9:30 AM (in response to mbabacek)Michal, proxies attribute is a list type, so you need to make sure you pass in a list:
[standalone@localhost:9990 /] /subsystem=modcluster/mod-cluster-config=configuration:write-attribute(name=proxies, value="my-proxies") { "outcome" => "failed", "failure-description" => "WFLYCTL0097: Wrong type for proxies. Expected [LIST] but was STRING", "rolled-back" => true } [standalone@localhost:9990 /] /subsystem=modcluster/mod-cluster-config=configuration:write-attribute(name=proxies, value=[my-proxies]) { "outcome" => "success", "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" } }
-
4. Re: Can registration by done by clients? Avoid multicast discovery?
rhusar May 10, 2016 9:35 AM (in response to bill.burke)Bill, the static configuration should look like:
- remove advertise-socket="modcluster"
- remove the respective modcluster binding
- configure advertise="false"
- add outbound-socket-binding for each proxy (see Michal's CLI command)
- configure proxies="" with a list of the created outbound-socket-binding (see above comment)
I have recently filed and submitted fixes for related issues: