Bug #1852: NoVNC Connection timeout with Firefox 15 - Foreman

Actions

Copy link

Bug #1852

closed

NoVNC Connection timeout with Firefox 15

Added by Jaroslav Henner over 12 years ago. Updated over 12 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Jaroslav Henner

Category:

VM management

Target version:

1.1

Difficulty:

trivial

Triaged:

Bugzilla link:

Pull request:

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

I'm using Foreman with libvirt with about 15 vms. I started getting Connection Timeout when displaying the noVNC. I managed to fix this problem by increasing some values in /usr/share/foreman/public/javascripts/noVNC/rfb.js:

    def_con_timeout  = Websock_native ? 5 : 15,

'disconnectTimeout',  'rw', 'int', 5,    'Time (s) to wait for disconnection'

Actions

Copy link

Updated by Ohad Levy over 12 years ago

Priority changed from High to Normal

do you have any idea why would it take more than 5 seconds to open a connection? is it a slow network?

Actions

Copy link

Updated by Jaroslav Henner over 12 years ago

I think libvirt may be too slow to response. But I think it is irrelevant what is causing such lag. I would expect there is no harm done if the timeout is increased. On the other hand, there is harm when it is too low!

On the other hand, from what I've found, TCP handshake sends 5 SYN packets, waiting no more than 200+800+1600+3200 = 5800ms.

Actions

Copy link

Updated by Ohad Levy over 12 years ago

ok, care to send a pull request / patch? :)

Actions

Copy link

Updated by Ohad Levy over 12 years ago

Subject changed from NoVNC Connection timeout when using libvirt to NoVNC Connection timeout with Firefox 15
Target version set to 1.1

ok, the real cause for this issue is described here:
https://bugzilla.mozilla.org/show_bug.cgi?id=789018

summary, FF15 opens too many connections at once, so the timeout fix (as shown in this patch and still waiting for a pull request) would be a workaround only for FF15.

Actions

Copy link