To clarify, the variables you've listed have never been part of the Docker image. Variables which correspond to properties controlling concurrency limits were added after the old properties were deprecated.
If you have a deployment where the deprecated properties were set, you can see what the new properties should be by checking the Tomcat logs. The warning about deprecation will contain instructions on what non-deprecated properties to set to what values to achieve the same effect. - Mike On Thu, Oct 18, 2018, 09:21 Tezarin <[email protected]> wrote: > Thank you, I'll review. I'm trying to see which ones will be replacing > the exact two variables I had listed. > On Thursday, October 18, 2018, 2:54:15 AM EDT, Mike Jumper < > [email protected]> wrote: > > The environment variables available for the Docker image are documented in > the manual: > > http://guacamole.apache.org/doc/gug/guacamole-docker.html# > guacamole-docker-mysql-optional-vars > > - Mike > > On Tue, Oct 16, 2018 at 9:16 AM, Tezarin <[email protected]> > wrote: > > > To be more specific, I am only looking for the current (non deprecated) > > values to replace these two variables: > > > > - MYSQL_DISALLOW_SIMULTANEOUS_CONNECTIONS= false - > > MYSQL_DISALLOW_DUPLICATE_CONNECTIONS= false > > Could you please advise what I should use instead? > > Thank you > > On Tuesday, October 16, 2018, 10:22:25 AM EDT, Tezarin > > <[email protected]> wrote: > > > > Thank you for your prompt reply. So in my case if these are the values I > > currently have in my docker-compose file: > > > > - MYSQL_DISALLOW_SIMULTANEOUS_CONNECTIONS= false - > > MYSQL_DISALLOW_DUPLICATE_CONNECTIONS= false > > > > What would be the equivalent if I were to adapt to the new > > variables?mysql-default-max-connections: 1 > > mysql-default-max-group-connections: 1 > > > > Thank you > > > > On Monday, October 15, 2018, 9:20:48 AM EDT, Mike Jumper < > > [email protected]> wrote: > > > > On Mon, Oct 15, 2018 at 5:49 AM, Tezarin <[email protected]> > > wrote: > > > > > > > > Good morning, > > > > > > > > > I understand the method I was using to fix the issue is deprecated, I > > > started all this by trying to avoid the error message in the guac user > > > interface about having too many connections open. In some cases, I was > > not > > > able to open a new guacamole connection (e.g. via RDB to a domain > > > controller) because guacamole thought I had too many open connections > > > already. (I can't remember if it thought I had too many connections to > > > this one domain controller already, or too many connections overall.) > > > > > > So ... how can we solve that problem? Should we solve that problem? > > > > > > > You use the new properties which replaced the older properties: > > > > http://guacamole.apache.org/doc/gug/jdbc-auth.html#jdbc-auth-concurrency > > > > You can also override this on a per-connection basis by specifying > > different values when editing the connection. > > > > - Mike > > > > >
