Bug 6146 - HA new session conflict code unnecessary or incomplete
Summary: HA new session conflict code unnecessary or incomplete
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: VSM Server (show other bugs)
Target Milestone: LowPrio
Assignee: Henrik Andersson
Depends on:
Reported: 2017-01-19 16:52 CET by Samuel Mannehed
Modified: 2021-04-16 09:33 CEST (History)
2 users (show)

See Also:
Acceptance Criteria:


Description Samuel Mannehed cendio 2017-01-19 16:52:45 CET
We have a section in the HA handling that deals with the case that a new session reported from the other node is in conflict with an existing session. We determine this conflict by looking at the agent/display pair.

However there are some questions here:

a) When can this ever occur? We haven't come up with any scenarios.

b) Is this even a problem? Reconnecting will verify and purge any broken sessions, so the only problem is one extra consumed license until the periodic check reaps it.

c) We only look at sessions for the same user as the incoming new session. However a display can conflict from a different user. This scenario is also easy to trigger if someone logs out and someone else logs in right after.
Comment 1 Bojan Memetovic cendio 2017-01-24 11:06:16 CET
Let start with A).
Comment 2 Samuel Mannehed cendio 2017-01-24 13:27:58 CET
(In reply to comment #1)
> Let start with A).

We decided to leave this bug on '---' for further discussions next week.
Comment 3 Pierre Ossman cendio 2021-04-16 09:33:34 CEST
We managed to trigger this code in bug 7683. Unfortunately we don't know how. So it seems it is possible, even if very rare.

Note You need to log in before you can comment on or make changes to this bug.