Do you think that people will use cluster with 2 nodes on localhost + embedded H2 + static loadbalancer in production? I guess not. So having our domain.xml "pre-set" to have easy example cluster setup won't help much IMO. Customers will be able to setup "easy" cluster in 5 minutes, but they will be unaware of all the steps they need to set the real "production" cluster.

Also there is inconsistency with Wildfly, which may lead to some other confusions (as you pointed in other thread for add-user script).

I think that what would be helpful is, to guide people through all the manual steps more deeply, so after "absolve" the tutorial, they will be able to set the domain with real production cluster in their environment with 2 remote nodes on different machines communicate between each other. And they will know the possibilities for setup real loadbalancer too (HTTPD+modcluster or Undertow+modcluster etc). But I am not sure how deep to go there, as loadbalancer is not directly our stuff...

Also maybe it would be helpful to have some guides for setup AWS or JGroups without Multicast, but with TCP and TCPPING. I know it's not our stuff, but you know... There were gazillion questions regarding this in last months ;-)


On 23/04/16 14:52, Bill Burke wrote:
This helps out with documenting domain mode to have an almost working example that I can walk through and explain.  The current distribution doesn't really help with that.  There's going to be more of this stuff.  This is why I wanted to start on documentation in January as I knew little usability things like this would pop up.  So, deal with it... 

Honestly, I should have just done this as I knew you were going to be a pain in the ass...

On 4/23/2016 1:31 AM, Stian Thorgersen wrote:

I vote against this. It's way to late to start making changes unless absolutely critical. At the moment we're just doing what WildFly/EAP does out of the box and I don't see any need for us to do different to them.

On 22 Apr 2016 20:43, "Bill Burke" <> wrote:
I'd like to make the following changes to domain.xml that we distribute
so that it runs as a cluster with a load balance out of the box on one

* remove the "default" profile.  Users should really only be using
domain mode with a cluster
* remove host.xml.  Its confusing to have both a host.xml and a
* host-master.xml will boot only 1 server ("server-one")
* host-slave.xml will boot only 1 server ("server-two")
* Pre-configure a undertow load balancer [1] to loadbalance between
server one and server two
* Point H2 to a shared directory under domain/servers

I've checked that this setup works on my laptop.  I hope to write a
Getting Started Guide around this too.


Bill Burke
JBoss, a division of Red Hat

keycloak-dev mailing list

Bill Burke
JBoss, a division of Red Hat

keycloak-dev mailing list