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 2024/08/29 17:34:00 UTC
[jira] [Comment Edited] (GUACAMOLE-600) Allow specifying connection timeout
[ https://issues.apache.org/jira/browse/GUACAMOLE-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877821#comment-17877821 ]
Mike Jumper edited comment on GUACAMOLE-600 at 8/29/24 5:33 PM:
----------------------------------------------------------------
[~vnick]: I've been doing some fiddling, and the issue seems related to the introduction of that {{fcntl()}} call setting the socket in non-blocking mode so we can have a connect timeout. I tried restoring the original flags at the end (under the assumption that things are failing because the caller is not expecting to receive a non-blocking socket), but that second call to {{fcntl()}} fails with {{EBADF}}. Removing _all_ calls to {{fcntl()}} such that the socket is a blocking socket "fixes" the issue (but presumably breaks the timeout).
was (Author: mike.jumper):
[~vnick]: I've been doing some fiddling, and the issue seems related to the introduction of that {{fcntl()}} call setting the socket in non-blocking mode so we can have a connect timeout. I tried restoring the original flags (under the assumption that things are failing because the caller is not expecting to receive a non-blocking socket), but that second call to {{fcntl()}} fails with {{EBADF}}. Removing _all_ calls to {{fcntl()}} such that the socket is a blocking socket "fixes" the issue (but presumably breaks the timeout).
> Allow specifying connection timeout
> -----------------------------------
>
> Key: GUACAMOLE-600
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-600
> Project: Guacamole
> Issue Type: New Feature
> Components: Documentation, RDP, SSH, Telnet, VNC
> Reporter: Nick Couchman
> Assignee: Nick Couchman
> Priority: Minor
> Fix For: 1.6.0
>
>
> This came up in a mailing list discussion, specifically related to SSH connections, but seems like it would be useful across all of the protocols to allow the connection to specify the timeout in making the connection. For environments where connections are expected to happen rapidly this can reduce delays if something is wrong; for environments that may experience larger delays it can avoid errors when the connection is expected to take a longer amount of time to establish.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)