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

emma commented on GUACAMOLE-567:
--------------------------------

Hi,

today i just build from github the release 1.0.0 with new improvements, 
patches, bug fixes on my Ubuntu Server 16.04.3 LTS (GNU/Linux 4.4.0-62-generic 
x86_64) with Tomcat8 and that's it, nothing more, nothing less.

This server is my test server and previously i was running github 1.0.0. 
version builded March the 3rd.

So i test connection on my differents servers (2003/2008/2012) and for most of 
them i notice i get during the first connection the message with logo about 
"Network connection unstable" despite the fact i am testing on my local 
network, not on remote through internet.

Then once im connected and Windows session is opened, i disconnect from my 
Windows server and the closing session seems to hang few seconds then i get 
connection error screen.

!Network_Connection1.png!

!Network_Connection2.png!

If i reconnect on the same server, this kind of message disappeared and 
disconnection seems to works fine on 2003 and 2008 servers. On my 2012 server i 
almost always get "Network connection unstable" and "error connection" message 
on disconnect !

It looks like, if there is a long time you didn't initiate a connection on a 
server, then you get "network connection unstable" message with logo, once you 
made at least one successful connection then disconnect works normally without 
any "connection error" screen, except on 2012 server where i almost always 
encounter this "problem" and message.

Or it is like at the very first connection on a server you get message during 
disconnection process

!Network_Connection4.png!

then you get the message

!Network_Connection5.png!

If i wait or click Reconnect and then cancel without logging for example, the 
disconnection works fine

!Network_Connection6.png!

Made another test with a  2003 Server and first time i am connecting on with 
that new version of guacamole, then i get the same behavior

!Network_Connection7.png!

!Network_Connection8.png!

It is just a test but before that "Network connection problem 
acknowledgement/feedback" case, i never have this behavior during disconnection 
screen !

Don't know if other testers can confirm that fact ?

Many thanks for your great job, Guacamole rocks !

 

> Network connection problem acknowledgement/feedback
> ---------------------------------------------------
>
>                 Key: GUACAMOLE-567
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-567
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: guacamole-client, guacamole-common-js
>            Reporter: Michael Jumper
>            Assignee: Michael Jumper
>            Priority: Major
>             Fix For: 1.0.0
>
>         Attachments: Network_Connection1.png, Network_Connection2.png, 
> Network_Connection4.png, Network_Connection5.png, Network_Connection6.png, 
> Network_Connection7.png, Network_Connection8.png, 
> image-2018-05-30-16-26-15-928.png, internal-error.png
>
>
> {panel:bgColor=#FFFFEE}
> *The description of this issue was copied from 
> [GUAC-1055|https://jira.glyptodon.org/browse/GUAC-1055], an issue in the JIRA 
> instance used by the Guacamole project prior to its move to the ASF.*
> Comments, attachments, related issues, and history from prior to acceptance 
> *may not have been copied* and can be found instead at the original issue.
> {panel}
> When Guacamole detects that the network connection is slow or hanging, it 
> should acknowledge this and unobtrusively notify the user. Lacking such 
> notification, slow networks or remote desktop failures look like Guacamole 
> bugs, and are frequently reported as such.
> Further, the total lack of a network connection is handled within JavaScript, 
> but the error code is not recognized by the Guacamole client. The unknown 
> error is thus translated into a generic "An internal error has occurred ..." 
> message, which is obviously incorrect:
> !internal-error.png|width=320!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to