Closed
Bug 1046576
Opened 11 years ago
Closed 11 years ago
Websocket connection timeout should default to 10 seconds in Loop server production
Categories
(Hello (Loop) :: Server, defect)
Hello (Loop)
Server
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: ferjm, Unassigned)
Details
(Whiteboard: [qa+])
We missed the configuration change introduced at [1] with the Loop server production release (0.9.2). This makes quite hard to do a FxOS Loop call as we are constantly getting a timeout (9 of 10 tries) so it would be great if we could do this configuration change in production.
[1] https://github.com/mozilla-services/loop-server/commit/25ddb4c6e4a2d392fda80ba23dd010a1d9b7bf69
| Reporter | ||
Updated•11 years ago
|
Flags: needinfo?(bwong)
Comment 1•11 years ago
|
||
The fix you're referring to is not part of loop-server 0.9.2, but is part of the upcoming 0.10.
What we can do, though, is change the configuration of the deployed 0.9.2 so it is set to 10.
Benson, would you be able to tweak this configuration variable in order to have a 10s delay?
| Reporter | ||
Comment 3•11 years ago
|
||
(In reply to Alexis Metaireau (:alexis) from comment #1)
> The fix you're referring to is not part of loop-server 0.9.2, but is part of
> the upcoming 0.10.
>
> What we can do, though, is change the configuration of the deployed 0.9.2 so
> it is set to 10.
> Benson, would you be able to tweak this configuration variable in order to
> have a 10s delay?
Yes, that's what I tried to mean in the description.
Comment 4•11 years ago
|
||
Comment 5•11 years ago
|
||
Deployed new configuration to prod. Timeout is now 10seconds.
https://github.com/mozilla-services/puppet-config/pull/749/files
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(bwong)
Resolution: --- → FIXED
Comment 6•11 years ago
|
||
:ferjm
:oteo
Can you verify the change matches expected behavior on your side?
Comment 7•11 years ago
|
||
Hi James,
Now I am able to establish the call without problem so the the timeout issue seems to be solved, thanks!
You need to log in
before you can comment on or make changes to this bug.
Description
•