Bug 34193 – Configurable Timeout for noVNC via UCR

Bug 34193 - Configurable Timeout for noVNC via UCR


Summary:	Configurable Timeout for noVNC via UCR

Status:	CLOSED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Virtualization - UVMM
Version:	UCS 4.2
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:

URL:
Keywords:

Depends on:	34116
Blocks:
	Show dependency tree / graph

Reported:	2014-02-25 12:09 CET by Tim Petersen
Modified:	2023-06-28 10:45 CEST (History)
CC List:	5 users (show)

See Also:	35428
What kind of report is it?:	Bug Report
What type of bug is this?:	2: Improvement: Would be a product improvement
Who will be affected by this bug?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	1: Nuisance – not a big deal but noticeable
User Pain:	0.011
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	Browser compatibility
Max CVSS v3 score:

Flags:	hahn: Patch_Available+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Tim Petersen

2014-02-25 12:09:33 CET

/usr/share/novnc/include/rfb.js:466
-> "conf.connectTimeout * 1000"

This controls the timeout for connection tries.

See also https://github.com/kanaka/noVNC/issues/238

Comment 1 Philipp Hahn

2014-03-20 09:42:04 CET

Erneut vom Kunden telefonisch nachgefragt.

Comment 2 Philipp Hahn

2017-05-03 16:58:53 CEST

Try to update to newer noVNC version virst: Bug #35428
Issue 238 was closed without any fix being applied; as such we should increment the timeout in our version by 2-4 by default:

core/rfb.js:556                 }.bind(this), this._disconnectTimeout * 1000);

Comment 3 Florian Best

2017-06-28 14:52:02 CEST

There is a Customer ID set so I set the flag "Enterprise Customer affected".

Comment 4 Ingo Steuwer

2020-07-03 20:53:51 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.