Eclipse Community Forums: Eclipse Scout

Help

Home

Home » Eclipse Projects » Eclipse Scout » Load Balancing

Show: Today's Messages :: Show Polls :: Message Navigator

Load Balancing [message #1853331]

Tue, 28 June 2022 06:55

Luka Cavic

Messages: 47
Registered: August 2014

Member

Hello,

before a month I wrote article on Stackoverflow about Load Balancing Eclipse Scout application with two tomcat instances and session sharing.

https://stackoverflow.com/questions/72421585/load-balancing-eclipse-scout-application

Is this statement correct that moving Scout application to another server is not possible because client model (desktop, outlines, forms, fields etc.) are not serializable?

Unfortunately, the classes that make up the client model (destop, outlines, forms, fields etc.) are not serializable. This means that they cannot be "moved" to other server instances. If a server goes down, all of its state is lost and cannot be recovered. Therefore, all users with a client session on that server are automatically logged out.

Report message to a moderator

Re: Load Balancing [message #1853332 is a reply to message #1853331]

Tue, 28 June 2022 07:03

Matthias Villiger

Messages: 232
Registered: September 2011

Senior Member

Hi Luka,

Yes this is correct. The person answering ('bsh') is one of our developers. Scout Classic's sessions are sticky (cannot be moved).
You can implement a load-balancing, but a session is bound to a single backend. On a failure of one cluster node, open dialogs, pages, etc. are lost and a new session (with authentication) may be created on another server.
The solutions provided by bsh are the correct options:

phase sessions out on a node before taking it down, does not solve the problem for an unplanned outage.
use a stateless architecture e.g. Scout JS instead of Scout Classic

Kind regards
Mat

Report message to a moderator