[
https://issues.apache.org/jira/browse/GUACAMOLE-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17551299#comment-17551299
]
Lee Doughty commented on GUACAMOLE-1126:
----------------------------------------
This issue came up again for my org, and looks like this issue is in the
ballpark of what we'd like.
I mentioned on the mailing list that our issue with this is mostly related to
never-ending server hassling... We've had users' browser start the reconnect
process and walk away, and the polling simply never stops...
I assume it's because their Guacamole session becomes one of a hundred tabs
they are not aware of... but despite this, their tab sits there poking our
Guacamole servers *~50 times an hour,* for {*}days{*}. The BEST solution I
found so far is to shut down the guacamole server so the user's client stops
polling... which is a terrible solution, so we gently roll over all users onto
new infrastructure over a 2-3 day period so eventually those people are talking
to infrastructure that doesn't exist.
This is also not a great solution, the better solution would be to perhaps hook
into how sessions are re-authenticated (which I'm not sure they can be, once
they get through the door once?)... or to do something _like this ticket_ – put
in some kind of reasonable maximum number of retry attempts (in some way)... or
exponentially back off the retries?
> 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.7#820007)
