On Sat, Jan 6, 2018 at 8:51 PM, Valeriu <vbala...@usc.edu> wrote: > The workaround that I found to work was to add two lines of code in the > client source code, then compile and update the guacamole war file in the > tomcat directory. > > Follow the steps for building the guacamole client from source code as > stated here > http://guacamole.apache.org/doc/gug/installing-guacamole. > html#building-guacamole-client > but before running the "mvn package" command edit the file > guacamole/src/main/webapp/app/client/controllers/clientController.js in a > basic text editor. > > In the text file, search for the line containing "// Determine whether the > reconnect countdown applies" and change the next line to be "var countdown > = > null;" to disable the auto-reconnect feature. >
I don't recommend doing this, as there are probably situations where it would be better if the auto-reconnect does actually happen. Completely disabling this behavior, across the entire Guacamole install, for all connections, seems ever so slightly excessive. With regard to the original post for this issue, there are a couple of things worth noting: - If you're using release 0.9.13-incubating or older, there is a bug for RDP connections that does not correct take into account why the RDP session ended. In certain situations this can cause an automatic reconnect when it would not normally happen, which may be contributing to the perception that this feature is not desirable. I suggest trying either the version in the current git master release, or waiting until 0.9.14 comes out see if that makes the issue any less bothersome. - There is also a JIRA issue ( https://issues.apache.org/jira/browse/GUACAMOLE-360) that deals with how Guacamole deals with a single user trying to start the same session from multiple locations. This may be of interest, depending on the scenario being discussed. -Nick
