0035440: tomcat clustering is restricted to sticky sessions

Description

When working in a clustered environment, it is not possible to move a session from one node to another. Forcing thus the cluster to be configured as sticky sessions, this is, once a session is created in a node, it must be served always by this same node.

This has two main inconvenients:
* It is not possible to load balance in case the node that is serving that session is highly loaded whereas there are other ones with lower load.
* In case the node serving that session fails, it will be required to re-login again in another one.

Steps To Reproduce

Tags

No tags attached.

Attached Files

Relationships [ Relation Graph ] [ Dependency Graph ]

depends on	design defect	0039400	closed	alostale	session is not Serializable
depends on	feature request	0039431	acknowledged	Triage Platform Base	mark application as distributable
related to	feature request	0040273	closed	alostale	show host name and background policy in about popup
blocks	design defect	0034490	acknowledged	Triage Platform Base	[clustering] Support clustering
Not all the children of this issue are yet resolved or closed.

Notes
There are no notes attached to this issue.

Issue History
Date Modified	Username	Field	Change
2017-03-07 09:53	alostale	New Issue
2017-03-07 09:53	alostale	Assigned To	=> platform
2017-03-07 09:53	alostale	OBNetwork customer	=> No
2017-03-07 09:53	alostale	Modules	=> Core
2017-03-07 09:53	alostale	Triggers an Emergency Pack	=> No
2017-03-07 09:53	alostale	Relationship added	blocks 0034490
2017-03-07 09:53	alostale	Status	new => acknowledged
2018-10-04 09:48	alostale	Relationship added	depends on 0039400
2018-10-10 13:17	alostale	Relationship added	depends on 0039431
2019-02-26 10:04	alostale	Relationship added	related to 0040273
2022-02-01 08:07	alostale	Assigned To	platform => Triage Platform Base