@Push stop after store HttpSession in distributed manner.

Vaadin 6 / 7 / 8
1

Hi guys
I have a Vaadin 7.1.13 application that stores HttpSession in Redis with Spring Session.

When I enable the application it will persist the session in Redis the screen updates via@Push (transport = Transport.WEBSOCKET_XHR)
stop happening.

Checking PushConnection of the UI is always with the status DISCONNECTED, if set @Push transport to WEBSOCKET it just work.

There is no error on the client and server console, does anyone have any idea of what may be happening?

[Example Code]
(https://github.com/Cleidiano/vaadin-distributed-session)

Regards

Cleidiano

2

I think it is somewhat related to these issues: https://github.com/vaadin/framework/issues/9188 and https://github.com/vaadin/framework/issues/8443 You could search other Redis related discussions on this Forum as well. My understanding is that this combination works only in very limited scenarios.

See more in these threads:

https://vaadin.com/forum/thread/16353391

https://vaadin.com/forum/thread/16400202

https://vaadin.com/forum/thread/14376541

Also the comment here about multiple browser tabs is about Flow: https://vaadin.com/forum/thread/17277282/spring-boot-vaadin-flow-spring-session-redis-spring-security-sessi, but is also valid for Vaadin Frameworks 7 & 8.

3

Hi, thanks for you reply.

I made some progress through hacking.

1 - Persist Sessions into redis.

2 - Connection push over websocket.(No websocket_xhr)

3 - No freeze browser after node on the clusters go down.

I will make some more test to verify application stability.

Regards

Cleidiano