You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "Mike Jumper (Jira)" <ji...@apache.org> on 2021/01/14 05:31:00 UTC
[jira] [Closed] (GUACAMOLE-1257) Unable to limit no of concurrent
users
[ https://issues.apache.org/jira/browse/GUACAMOLE-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Jumper closed GUACAMOLE-1257.
----------------------------------
Resolution: Invalid
Retesting these myself, I can confirm that these parameters all work correctly. The limits are correctly enforced.
[~reuben_r0d], make sure you restarted Tomcat so that your configuration changes are applied. If you're still having trouble, open a thread on the user@guacamole.apache.org mailing list, and the community should be able to help troubleshoot.
> Unable to limit no of concurrent users
> --------------------------------------
>
> Key: GUACAMOLE-1257
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1257
> Project: Guacamole
> Issue Type: Bug
> Affects Versions: 1.2.0
> Environment: Debian 10, GCP
> Reporter: Reuben Rodrigues
> Priority: Minor
>
> *How to reproduce?*
> 1. Set the following parameters with values of one:
> * {{mysql-absolute-max-connections}}
> * {{mysql-default-max-connections}}
> * {{mysql-default-max-group-connections}}
> * {{mysql-default-max-connections-per-user}}
> * {{mysql-default-max-group-connections-per-user}}
> 2. When the same user tries to access another instance of Guacamole from another tab he is allowed
>
> *Expected Behavior*
> Only one user should be able to connect at a given time
>
> Am I missing anything in the settings here? Any help would be appreciated.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)