<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Zookeeper is part of the Fabric architecture. I may be an option in the context of this conversation, but its not something that we have already readily available.<div class=""><br class=""></div><div class="">In the most simplistic scenario, we have a remote Camel Http client that wants to connect to cluster of wildfly servers that expose undertow endpoints. The Camel client wants to use a <a href="http://camel.apache.org/load-balancer.html" class="">load balancer</a> like this</div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><font face="Courier New" size="1" class=""><camelContext id="camel" xmlns="<a href="http://camel.apache.org/schema/spring" class="">http://camel.apache.org/schema/spring</a>"><br class=""></font><font face="Courier New" size="1" class=""> <route><br class=""></font><font face="Courier New" size="1" class=""> <from uri="direct:start"/><br class=""></font><font face="Courier New" size="1" class=""> <loadBalance> <br class=""></font><font face="Courier New" size="1" class=""> <roundRobin/><br class=""></font><font face="Courier New" size="1" class=""> <to uri="mock:x"/> <br class=""></font><font face="Courier New" size="1" class=""> <to uri="mock:y"/> <br class=""></font><font face="Courier New" size="1" class=""> <to uri="mock:z"/> <br class=""></font><font face="Courier New" size="1" class=""> </loadBalance><br class=""></font><font face="Courier New" size="1" class=""> </route></font><div class=""><font face="Courier New" size="1" class=""></camelContext> </font></div><div class=""><font face="Courier New" size="1" class=""><br class=""></font></div></blockquote><div class=""><div class="">I now wonder if it is possible to implement a camel load balancer variant that is able to discover the initial topology of wildfly http endpoints and later react on changes in that topology. Does that make sense?</div><div class=""><br class=""></div><div class="">cheers</div><div class="">— thomas</div><div class=""><br class=""></div><div><blockquote type="cite" class=""><div class="">On 27 Nov 2015, at 00:09, Stuart Douglas <<a href="mailto:sdouglas@redhat.com" class="">sdouglas@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">I'm not really sure exactly what you mean here, do you want the Undertow load balancer to be able to use the data from the zookeper registry? Or are you talking about having the Undertow endpoints register themselves with zookeeper?<br class=""><br class="">Stuart<br class=""><br class="">----- Original Message -----<br class=""><blockquote type="cite" class="">From: "Thomas Diesler" <<a href="mailto:tdiesler@redhat.com" class="">tdiesler@redhat.com</a>><br class="">To: "Stuart Douglas" <<a href="mailto:sdouglas@redhat.com" class="">sdouglas@redhat.com</a>><br class="">Cc: <a href="mailto:wildfly-dev@lists.jboss.org" class="">wildfly-dev@lists.jboss.org</a><br class="">Sent: Thursday, 26 November, 2015 1:03:16 AM<br class="">Subject: Allow Camel LoadBalancer to connect to clustered WildFly HTTP endpoints<br class=""><br class="">Hi Stuart/Friends,<br class=""><br class=""><a href="https://github.com/wildfly-extras/wildfly-camel/issues/878" class="">https://github.com/wildfly-extras/wildfly-camel/issues/878</a><br class=""><https://github.com/wildfly-extras/wildfly-camel/issues/878><br class=""><br class="">In fabric a camel load balancer can contact a (zookeeper) registry using a<br class="">logical name to react to changes in server topology or for initial<br class="">discovery. I wonder how this can/should be done in the context of undertow<br class="">http endpoints on wildfly.<br class=""><br class="">cheers<br class="">— thomas<br class=""></blockquote><br class="">_______________________________________________<br class="">wildfly-dev mailing list<br class=""><a href="mailto:wildfly-dev@lists.jboss.org" class="">wildfly-dev@lists.jboss.org</a><br class="">https://lists.jboss.org/mailman/listinfo/wildfly-dev</div></div></blockquote></div><br class=""></div></body></html>