montagnahuanghsiao commented on issue #14097:
URL: https://github.com/apache/cloudstack/issues/14097#issuecomment-5601517245
### Additional timeout configuration evidence
The current CloudStack global setting is:
`consoleproxy.session.timeout = 28800000`
This corresponds to 8 hours:
`28800000 ms = 8 hours`
However, during the reproduced noVNC console failure, the Console Proxy VM
logged:
`Idle timeout expired: 300001/300000 ms`
The effective Jetty WebSocket idle timeout was therefore still 300000 ms
(5 minutes), rather than the configured 28800000 ms (8 hours).
The affected Console Proxy implementation also appears to contain a separate
hard-coded value:
`ConsoleProxy.VIEWER_LINGER_SECONDS = 180`
This creates three different timeout values that may affect the same console
session lifecycle:
- Configured `consoleproxy.session.timeout`: 28800000 ms (8 hours)
- Observed Jetty WebSocket idle timeout: 300000 ms (5 minutes)
- `ConsoleProxy.VIEWER_LINGER_SECONDS`: 180 seconds (3 minutes)
This may explain why the console can disconnect after approximately
2–5 minutes even though the configured session timeout is 8 hours.
The console was actively being used when the disconnection occurred. The
guest
VM remained Running, the Console Proxy VM remained Running with Agent State
Up,
and reopening the console from the CloudStack UI immediately worked with a
new
access token.
Could you please confirm:
1. Whether the Jetty WebSocket idle timeout is expected to use
`consoleproxy.session.timeout`.
2. Whether `ConsoleProxy.VIEWER_LINGER_SECONDS` is expected to remain
hard-coded at 180 seconds.
3. Whether PR #13002 makes both the WebSocket timeout and viewer
garbage-collection timeout honor `consoleproxy.session.timeout`.
4. Whether the fix is included in any released or planned 4.22 package.
5. Whether changing `consoleproxy.session.timeout` requires restarting the
Management Server, restarting the Console Proxy VM, or recreating the
Console Proxy VM.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
