You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@guacamole.apache.org by "Michael Jumper (JIRA)" <ji...@apache.org> on 2018/04/02 06:35:00 UTC
[jira] [Created] (GUACAMOLE-533) Automatically kill wayward guacd
processes
Michael Jumper created GUACAMOLE-533:
----------------------------------------
Summary: Automatically kill wayward guacd processes
Key: GUACAMOLE-533
URL: https://issues.apache.org/jira/browse/GUACAMOLE-533
Project: Guacamole
Issue Type: Improvement
Components: guacd
Reporter: Michael Jumper
The cleanup mechanisms of all supported protocols and guacd itself currently depend on the underlying client library being well behaved. In general, this works well, but there exist circumstances where bugs in an underlying library result in the process hanging, spinning, etc., despite the actual Guacamole side of the connection having entered a disconnected state. If this occurs, the process handling the connection never terminates.
The handling of each connection process should be modified such that a failsafe kicks in if disconnect is not handled in a timely manner. If the Guacamole side of a connection closes, the protocol support should have some reasonable amount of time to finish its own cleanup, after which guacd should assume the worst and forcibly kill the process, allowing the OS to reclaim resources.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)