Defect #281
Cannot load waves, frequently (video)
Status: | Closed | Start date: | ||
---|---|---|---|---|
Priority: | Urgent | Due date: | ||
Assignee: | Vicente J. Ruiz Jurado | % Done: | 100% | |
Category: | WIAB Server | |||
Target version: | - | |||
Resolution: | Tags: |
Description
Ticket from Stas, with video of the behaviour:
http://samer.ourproject.org/++/loading.ogv
He basically cannot use Kune. FF 12 in Linux.
Related issues
Associated revisions
Updating jetty, trying to solve #281
History
#1 Updated by Stanislav German-Evtushenko over 12 years ago
Any ideas how can it be fixed?
#2 Updated by Stanislav German-Evtushenko over 12 years ago
Just moved to another laptop with FF 11.0. No proxy and problem is just the same. I can open most of threads but those are with undread messages are not likely to be opened. Repeating refresh many times helps sometimes.
#3 Updated by Vicente J. Ruiz Jurado over 12 years ago
I'm spending a lot of time trying to fix this. I think that now the situation is "better" but not totally fixed. Anyway I think is happening with very less frequency.
Can you try now and give me feedback?
#4 Updated by Stanislav German-Evtushenko over 12 years ago
Much better now. Sometimes I have to change between waves to open properly one of them but no they don't hang on "loading" as before.
#5 Updated by Stanislav German-Evtushenko over 12 years ago
I can't open "wave mocks". Sometimes it opens after browser refresh.
#6 Updated by Vicente J. Ruiz Jurado over 12 years ago
Yes, it's veryyyy strange. I don't find any explanation or fix, and well, I'm debugging, trying to catch the bug. Seems like a deadlock.
#7 Updated by Vicente J. Ruiz Jurado over 12 years ago
We'll more info:
https://issues.apache.org/jira/browse/WAVE-358
that brings some light to this issue.
#8 Updated by Vicente J. Ruiz Jurado over 12 years ago
Sometimes if the wave does not open immediately, to click again in the same wave, forces to open it (not always works, but, sometimes).
Maybe is related with:
https://jira.codehaus.org/browse/JETTY-1463
I'll do some comment there.
#9 Updated by Vicente J. Ruiz Jurado over 12 years ago
- Priority changed from High to Urgent
Another workaround for Firefox. In "about:config" put network.websocket.enabled to false and reload kune.
#10 Updated by Samer - over 12 years ago
Confirmed what Vicente was saying in comment #9, the workaround disabling websockets makes it work perfectly...
#11 Updated by Stanislav German-Evtushenko over 12 years ago
Workaround was working at first but now I can't even open Kune with that option disabled.
#12 Updated by Vicente J. Ruiz Jurado over 12 years ago
I have just updated kune, so, try to refresh your browser...
#13 Updated by Stanislav German-Evtushenko over 12 years ago
I can't open https://kune.cc/?locale=en#!movecommons.lists.1074.2810 with socket disabled and the wave is not likely to load if socket is enabled.
#14 Updated by Vicente J. Ruiz Jurado over 12 years ago
Please, try it again.
For all of us: If the problem persist, please leave a comment (I've disabled SSL).
#15 Updated by Stanislav German-Evtushenko over 12 years ago
I can't open any of waves now.
#16 Updated by Vicente J. Ruiz Jurado over 12 years ago
Reload your browser... and if persist, please check your network petitions with firebug.
(I can work open all my waves with two browsers).
#17 Updated by Vicente J. Ruiz Jurado over 12 years ago
One more comment. Websocket does not work under normal proxies. Are you under a proxy when you cannot open any wave?
#18 Updated by Stanislav German-Evtushenko over 12 years ago
Vicente J. Ruiz Jurado wrote:
One more comment. Websocket does not work under normal proxies. Are you under a proxy when you cannot open any wave?
Yes, as I'm at work place now. It worked before (was unstable but worked).
#19 Updated by Stanislav German-Evtushenko over 12 years ago
works well without proxy
#20 Updated by Samer - over 12 years ago
Confirmed, now everything works smoothly (FF13, Ubuntu, websockets enabled).
With websockets disabled, for some reason it cannot open my Bio in groupspace (which opens fine if enabled), but it does open the rest of the waves (in inbox and groupspace).
#21 Updated by Vicente J. Ruiz Jurado over 12 years ago
So we can confirm that is a SSL issue, right?. I was trying to find a bug or a reason why some SSL packets are dropped, but without success. Anyway I think that I found a way to avoid the situation. I'll test it the next week.
#22 Updated by Vicente J. Ruiz Jurado about 12 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
This is fixed.
#23 Updated by Stanislav German-Evtushenko about 12 years ago
nice to know!