You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "Bap (Jira)" <ji...@apache.org> on 2022/01/20 04:05:00 UTC

[jira] [Commented] (GUACAMOLE-1126) Implement Maximum auto-reconnect attempts

    [ https://issues.apache.org/jira/browse/GUACAMOLE-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479089#comment-17479089 ] 

Bap commented on GUACAMOLE-1126:
--------------------------------

Hi [~erodriguez19] and everybody, Hope you doing well,

I have a situation where I design a system for more than 200 people concurrently accessing an RDP session. I plan to choose Guacamole because I love Opensource

But the problem is when I configure Load Balancers with Guacamole servers as upstreams, following the round-robin model. It seems that Guacamole only supports stickiness sessions so when designing a load balancing system (maintaining a connection of 1 user corresponding to 1 backend persistently),

It does not mean load sharing between servers.

As you said above can serve more than 60 users at the same time, so please help me with advice on how I will design with my problem.

Thanks much

> Implement Maximum auto-reconnect attempts
> -----------------------------------------
>
>                 Key: GUACAMOLE-1126
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1126
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: guacamole-client
>            Reporter: Edgardo Rodriguez
>            Priority: Minor
>
> Using guacamole for 60+ users I've realized that sometimes, RDP hosts "go away" because of hardware issues, dns issues, etc and users might not be aware of it. 
>  For example, they leave their computer with the browser open with session established and going on... When this happens, Guacamole tries to auto-reconnect every 15 seconds without any limitation (some times indefinitely) and also, SESSION TIMER is renewed because of fake? user activity.
>  I've implemented a counter which allows automatic reconnection attempts for up to 4 tries. When tried 4 times, countdown timer is not further applied and so user is left with manual Reconnect dialog prompt as usual.
> I `ve not implemented a visual indication like 1/4 2/4,etc because it involves transalations and other "more complex" stuff.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)