[ https://issues.apache.org/jira/browse/GUACAMOLE-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17152135#comment-17152135 ]
Nick Couchman commented on GUACAMOLE-1126: ------------------------------------------ [~erodriguez19]: I think we've discussed this in the past as something we'd like to implement; however, I would suggest that it be a configurable setting rather than a set number of tries, and that it default to continuous retries (the current behavior) unless otherwise configured. This should likely be a Connection Attribute (vs. Parameter), similar to the load balancing stuff. I also think it's probably worth taking the time to work through implementing the counter (1/4, 2/4, etc.) - we can help you through that. Feel free to submit the pull request (maybe put it in draft mode) and we can work through it. > 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)