[GUACAMOLE-1796] Default batch size for SQL Server is too large

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.5.2
• Fix Version/s: 1.5.3
• Component/s: Documentation, guacamole-auth-jdbc-sqlserver
• Environment: docker
• Assignee: Unassigned
• Reporter: Chris Johnson
• Created: 31/May/23 14:04
• Updated: 16/Jul/23 23:02
• Resolved: 16/Jul/23 23:02

Description

We have a rather large number of connections and after logging in, I'm getting "An error occurred and this action cannot be completed".

In the Guacamole log I'm getting the following error:

^{### Error querying database.  Cause: com.microsoft.sqlserver.jdbc.SQLServerException: The incoming request has too many parameters. The server supports a maximum of 2100 parameters. Reduce the number of parameters and resend the request.
### The error may exist in org/apache/guacamole/auth/jdbc/connection/ConnectionMapper.xml
### The error may involve defaultParameterMap
### The error occurred while setting parameters
### SQL: SELECT             [guacamole_connection].connection_id,             [guacamole_connection].connection_name,             parent_id,             protocol,             max_connections,             max_connections_per_user,             proxy_hostname,             proxy_port,             proxy_encryption_method,             connection_weight,             failover_only,             (                 SELECT MAX(start_date)                 FROM [guacamole_connection_history]                 WHERE [guacamole_connection_history].connection_id = [guacamole_connection].connection_id             ) AS last_active         FROM [guacamole_connection]         WHERE [guacamole_connection].connection_id IN << A load of question marks >> ### Cause: com.microsoft.sqlserver.jdbc.SQLServerException: The incoming request has too many parameters. The server supports a maximum of 2100 parameters. Reduce the number of parameters and resend the request.}

I believe that there was a similar issue that was fixed in GUACAMOLE-1253 but for the number of users.

I have attached the log if that helps.

At the moment, the platform is unusable for ourselves.

Issue Links

• relates to: GUACAMOLE-1253 Hitting 2100 SQLServer query parameter limit with large user base