SessionManager keeps state of last component only

Description

SessionManager has a Cache that holds external components, mapped to the cluster node ID of the cluster node that they're connected to.

External components can connect more than once to the same server (see ). If that's true, then it stands to reason that they can also connect to more than one cluster node.

The current implementation maps the component to exactly one cluster node. That will introduce problems, when the component is connected to more than one node.

Environment

None
Fixed
Your pinned fields
Click on the next to a field label to start pinning.

Assignee

Dave Cridland

Reporter

Guus der Kinderen