Sticky sessions when using wildfly as load balancer

[hfluz]

I have 3 servers:

• Server one as a load balancer.
• Server two and server three with my Java EE deployments.

Server one contains a Wildfly server configured according to the documentation: https://docs.jboss.org/author/display/WFLY10/Using+Wildfly+as+a+Load+Balancer

It kinda worked, but I noticed the session doesn't stick to a server. It gets alternating all the time between servers two and three.

I'd like to know if there's any configuration not presented in the documentation to enable sticky sessions.

[rhusar]

Sounds like you are hitting undertow bug [UNDERTOW-635] mod_cluster incorrectly parses out route: strips everything after '.' in the route - JBoss Issue Tracker that causes sticky sessions to be broken, can you check that?

[hfluz]

To be honest, I'm not sure how to reproduce the issue again.

I tried another time, I started servers 2 and 3 in domain mode, and this time I got the opposite problem.

The load balancer does never balance to the server 2, it always forward requests to server 3. It seems it consider the order in which they are declared in the handler:

<reverse-proxy name="my-handler">

          <host name="host2" outbound-socket-binding="srv217" scheme="ajp" instance-id="myroute" path="/"/>

          <host name="host1" outbound-socket-binding="srv216" scheme="ajp" instance-id="myroute" path="/"/>                   

</reverse-proxy>

Then I removed host2 from the handler, and I noticed host1 was not being accessed at all from the balancer.

This remote proxy feature is seeming a little unpredictable for me, if I manage to reproduce the original issue again, I'll answer this thread.

[rhusar]

Ok, sorry, I thought you were talking about modcluster, now I see you are talking about static configuration.