[
https://issues.apache.org/jira/browse/GUACAMOLE-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17291065#comment-17291065
]
Mike Jumper commented on GUACAMOLE-1126:
----------------------------------------
The automatic reconnect shouldn't occur if the connection is closed due to
invalid login. There are specific error codes returned by the RDP server that
indicate the reason for the disconnect, and Guacamole should be transforming
those codes into its own which are handled client-side. The automatic reconnect
then only takes place when the nature of the error is likely to be transient
and resolved after a reconnect.
> 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.3.4#803005)
