Open bardyamomeni opened 1 year ago
This is somehow expected because of how Spring Session deserialize and serialize the session at every request.
Take a look at the following issues
@mcollovati Thanks for the information
That is very odd behaviour from the Vaadin team, they provide something that does not work (distributed session), and expect the user to pay for the fix by having the Kubernetes kit? That is not a sustainable approach IMHO!
I think having the foundation of HA available to users free of charge is a must!
I hope this problem gets attention!
You can archive high availability by using Sticky Sessions and a properly configured proxy server which allows draining of sessions pretty easily.
What @knoobie said, there is also a blog post describing how to use Hazelcast with Vaadin: https://vaadin.com/blog/vaadin-and-hazelcast-a-match-made-in-heaven.
Same behaviour is also observed when you add JDBC based Sessions
Description of the bug
Whenever instead of normal HTTP sessions I try to use distributed sessions using Hazelcast, trying to load the Vaadin app causes recursive refresh.
Removing the hazelcast session and switching to local session solves the problem.
Expected behavior
The app should be shown instead of getting trapped in refresh loop
Minimal reproducible example
just add
with hazelcast bean
Versions