[ 
https://issues.apache.org/jira/browse/GUACAMOLE-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15644821#comment-15644821
 ] 

Michael Jumper commented on GUACAMOLE-115:
------------------------------------------

{quote}
I'm also having an modified webapp based on client 0.9.3 running excellent with 
server 0.9.10 incubation except this problem.
{quote}

It is *not* safe to combine 0.9.3 with 0.9.10. There are protocol-level 
differences which are incompatible. You should only ever use guacamole-client 
and guacamole-server together if they are same version.

Can you confirm that the issue you report for SSH does not occur when using 
compatible versions of client and server (ie: both 0.9.10-incubating)?

{quote}
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
{quote}

Are these RDP sessions to the same RDP server, with the same user?

{quote}
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"
{quote}

Are you manually logging out of the first RDP session, or is it that Windows is 
kicking you out of the first session (due to a second identical RDP session 
being started)?

> 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)

Reply via email to