[
https://issues.apache.org/jira/browse/GUACAMOLE-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297057#comment-15297057
]
Michael Jumper commented on GUACAMOLE-34:
-----------------------------------------
This is caused by the lack of {{guac_client_abort()}} or {{guac_client_stop()}}
call in some cases where the client thread otherwise terminates. The connection
will full close under ONLY the following circumstances:
# All users disconnect (close their browser tabs, manually select "Disconnect"
within the guac menu, etc.)
# {{guac_client_stop()}} is called
# {{guac_client_abort()}} is called
If the internal client disconnects and terminates its own thread, it should
also invoke {{guac_client_stop()}} or {{guac_client_abort()}} to ensure
connected users are forced off. Otherwise, users will be confused why their
connection remains active with an unresponsive remote desktop session.
> RDP connection does not close
> -----------------------------
>
> Key: GUACAMOLE-34
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-34
> Project: Guacamole
> Issue Type: Bug
> Reporter: Michael Jumper
> Priority: Critical
>
> When an RDP connection is established, and the user manually disconnects by
> clicking "Logoff" or "Disconnect" in the start menu, the connection is logged
> as terminated by guacd yet no "Disconnected" dialog appears within the
> browser window.
> This does not occur for SSH.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)