[
https://issues.apache.org/jira/browse/GUACAMOLE-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15644900#comment-15644900
]
Michael Jumper commented on GUACAMOLE-115:
------------------------------------------
Attempting this myself, I can confirm the effect, though the duplicate SSH/RDP
connection aspect seems to be a coincidence which just happens to make the
issue more likely to occur.
I can confirm that guacd logs that the connection has closed essentially
immediately upon the disconnect expected. The problem is that the socket read
within the web application continues to block despite the TCP connection being
closed. Eventually, the JavaScript side gives up on receiving data and closes
the connection, reporting a server timeout. That results in things getting
cleaned up within the web application, and things finally close down.
> Two or more RDP/SSH Sessions and only the last one created terminates
> correctly
> -------------------------------------------------------------------------------
>
> Key: GUACAMOLE-115
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-115
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole
> Affects Versions: 0.9.10-incubating
> Environment: CentOS 7.x and Tomcat 8.0.37
> Guacamole 0.9.10 current master server and client
> Reporter: Werner Novak
>
> When creating two or more rdp/ssh sessions from the same type, only the last
> created session terminates correctly.
> Procedure to reproduce:
> 1. open first rdp session
> 2. open second rdp session
> 3. logout first rdp session the logout takes long time until timeout with
> message "The connection has been closed because the server is taking too long
> too respond"
> 4. logout second rdp session logout runs fine with message "You have been
> disconnected"
> This is reproducable !
> I'm also having an modified webapp based on client 0.9.3 running excellent
> with server 0.9.10 incubation except this problem.
> There the procedure looks like this:
> 1. open first ssh session
> 2. open second ssh session
> 3. exit first ssh session, the screen hangs at logoff
> 4. exit second ssh session, than both sessions are closed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
