Eclipse Community Forums: Eclipse Scout

Home » Eclipse Projects » Eclipse Scout » Load Balancing

Tue, 28 June 2022 02:55

Eclipse User

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.

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

Tue, 28 June 2022 03:03

Eclipse User

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

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

Tue, 28 June 2022 03:13

Eclipse User

That was fast reply :) Thank you!

Previous Topic:	BeanCreationException: could not create bean class for a LookupService
Next Topic:	Error code 403 by Database authentication

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Jun 13 23:17:15 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter