[
https://issues.apache.org/jira/browse/GUACAMOLE-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024126#comment-17024126
]
Mike Jumper commented on GUACAMOLE-919:
---------------------------------------
It's also possible there may be a way to configure the connection pool to
attempt to keep the connections alive with more frequent pings. It may be that
the database is timing out large numbers of connections within the pool,
causing delays and errors when attempts to query the database end up needing to
iterate through the entire pool of dead connections before it's finally emptied
and new connections are created.
I don't see this in my own deployment, which uses PostgreSQL, but there may be
(uncommon?) configuration or environmental differences that cause this to occur.
> An I/O error occurred while sending to the backend
> --------------------------------------------------
>
> Key: GUACAMOLE-919
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-919
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-auth-jdbc-postgresql
> Affects Versions: 1.0.0
> Reporter: Mechanix
> Assignee: Nick Couchman
> Priority: Minor
> Attachments: image-2020-01-27-15-19-26-634.png
>
>
> Hi,
> we use guacamole with postgresql and openid extension. Guacamole and guacd is
> deployed inside a k8s cluster.
> For some reason, the authentication doesn't succeed sporadically; there is
> only a blank page and this error message in the guacamole log:
> *[pool-1-thread-1] WARN o.a.i.d.pooled.PooledDataSource - Execution of ping
> query 'SELECT 1' failed: An I/O error occurred while sending to the backend.*
> I suspect there is a weird timeout happening between guacamole and postgresql
> but could figure out why.
> Any hints are much appreciated. Thanks
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
