It doesn't say webapp failing back to HTTP, but looks like Guacamole is using
HTTP tunnel instead of WebSocket, not sure if this is default.
Note " Using HTTP tunnel (not WebSocket). Performance may be sub-optimal."
occur when initiating file transfer from remote system.
Another question is, does ssh host verification play any role in transferring
files ?.
I have restarted nginx, guacad and tomcat9, still no joy.
nginx configuration support websocket.
*********************************************
location /jump/ {
proxy_pass http://localhost:8080;
proxy_buffering off;
proxy_http_version 1.1;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
client_max_body_size 1g;
access_log off;
}
log outputs.
*********************************************
tail -f /var/log/tomcat9/catalina.out
[2024-01-12 09:31:31] [info] 09:31:31.027 [http-nio-8080-exec-7] WARN
o.a.i.d.pooled.PooledDataSource - Execution of ping query 'SELECT 1' failed:
The last packet successfully received from the server was 62,273,492
milliseconds ago. The last packet sent successfully to the server was
62,273,492 milliseconds ago. is longer than the server configured value of
'wait_timeout'. You should consider either expiring and/or testing connection
validity before use in your application, increasing the server configured
values for client timeouts, or using the Connector/J connection property
'autoReconnect=true' to avoid this problem.
[2024-01-12 09:31:31] [info] 09:31:31.029 [http-nio-8080-exec-7] WARN
o.a.i.d.pooled.PooledDataSource - Execution of ping query 'SELECT 1' failed:
The last packet successfully received from the server was 62,273,490
milliseconds ago. The last packet sent successfully to the server was
62,273,490 milliseconds ago. is longer than the server configured value of
'wait_timeout'. You should consider either expiring and/or testing connection
validity before use in your application, increasing the server configured
values for client timeouts, or using the Connector/J connection property
'autoReconnect=true' to avoid this problem.
[2024-01-12 09:31:31] [info] 09:31:31.030 [http-nio-8080-exec-7] WARN
o.a.i.d.pooled.PooledDataSource - Execution of ping query 'SELECT 1' failed:
The last packet successfully received from the server was 62,263,439
milliseconds ago. The last packet sent successfully to the server was
62,263,439 milliseconds ago. is longer than the server configured value of
'wait_timeout'. You should consider either expiring and/or testing connection
validity before use in your application, increasing the server configured
values for client timeouts, or using the Connector/J connection property
'autoReconnect=true' to avoid this problem.
[2024-01-12 09:31:42] [info] 09:31:42.398 [http-nio-8080-exec-10] INFO
o.a.g.r.auth.AuthenticationService - User "eby.mani" successfully authenticated
from \public-ip.
[2024-01-12 09:31:55] [info] 09:31:55.544 [http-nio-8080-exec-3] INFO
o.a.g.r.auth.AuthenticationService - User "eby.mani" successfully authenticated
from \public-ip.
[2024-01-12 09:32:08] [info] 09:32:08.161 [http-nio-8080-exec-6] INFO
o.a.g.r.auth.AuthenticationService - User "eby.mani" successfully authenticated
from \public-ip.
[2024-01-12 09:32:17] [info] 09:32:17.657 [http-nio-8080-exec-10] INFO
o.a.g.tunnel.TunnelRequestService - User "eby.mani" connected to connection
"20".
[2024-01-12 09:32:17] [info] 09:32:17.658 [http-nio-8080-exec-10] INFO
o.a.g.t.h.RestrictedGuacamoleHTTPTunnelServlet - Using HTTP tunnel (not
WebSocket). Performance may be sub-optimal.
[2024-01-12 09:32:54] [info] 09:32:54.385 [http-nio-8080-exec-10] INFO
o.a.g.tunnel.TunnelRequestService - User "eby.mani" disconnected from
connection "20". Duration: 36727 milliseconds
[2024-01-12 09:32:54] [info] 09:32:54.390 [http-nio-8080-exec-2] INFO
o.a.g.tunnel.TunnelRequestService - User "eby.mani" disconnected from
connection "20". Duration: 36732 milliseconds
[2024-01-12 09:32:54] [info] 09:32:54.404 [http-nio-8080-exec-5] WARN
o.a.g.s.GuacamoleHTTPTunnelServlet - HTTP tunnel request rejected: No such
tunnel.
[2024-01-12 09:32:54] [info] 09:32:54.577 [http-nio-8080-exec-1] WARN
o.a.g.s.GuacamoleHTTPTunnelServlet - HTTP tunnel request rejected: No such
tunnel.
*********************************************
Thanks.
On Friday, 12 January, 2024 at 01:53:43 am IST, Michael Jumper
<mjum...@apache.org> wrote:
Do you see any messages in the Guacamole (not guacd) logs noting that
the webapp is falling back to using HTTP as WebSocket could not be used?
There may be something interfering with use of WebSocket. If this
happens, the HTTP tunnel will kick in and alternate between a pair of
HTTP connections to achieve the same kind of streaming, and that will
prevent downloading files due to browser throttling of HTTP requests:
https://issues.apache.org/jira/browse/GUACAMOLE-506
- Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@guacamole.apache.org
For additional commands, e-mail: user-h...@guacamole.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@guacamole.apache.org
For additional commands, e-mail: user-h...@guacamole.apache.org
