[wildfly-dev] Allow Camel LoadBalancer to connect to clustered WildFly HTTP endpoints
tdiesler at redhat.com
Fri Nov 27 02:43:22 EST 2015
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.
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 load balancer <http://camel.apache.org/load-balancer.html> like this
<camelContext id="camel" xmlns="http://camel.apache.org/schema/spring">
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?
> On 27 Nov 2015, at 00:09, Stuart Douglas <sdouglas at redhat.com> wrote:
> 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?
> ----- Original Message -----
>> From: "Thomas Diesler" <tdiesler at redhat.com>
>> To: "Stuart Douglas" <sdouglas at redhat.com>
>> Cc: wildfly-dev at lists.jboss.org
>> Sent: Thursday, 26 November, 2015 1:03:16 AM
>> Subject: Allow Camel LoadBalancer to connect to clustered WildFly HTTP endpoints
>> Hi Stuart/Friends,
>> In fabric a camel load balancer can contact a (zookeeper) registry using a
>> logical name to react to changes in server topology or for initial
>> discovery. I wonder how this can/should be done in the context of undertow
>> http endpoints on wildfly.
>> — thomas
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the wildfly-dev