Kune

Any ideas how can it be fixed?

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.

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?

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.

I can't open "wave mocks". Sometimes it opens after browser refresh.

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.

We'll more info:
https://issues.apache.org/jira/browse/WAVE-358
that brings some light to this issue.

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.

Confirmed what Vicente was saying in comment #9, the workaround disabling websockets makes it work perfectly...

Workaround was working at first but now I can't even open Kune with that option disabled.

I have just updated kune, so, try to refresh your browser...

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.

Please, try it again.

For all of us: If the problem persist, please leave a comment (I've disabled SSL).

I can't open any of waves now.

Reload your browser... and if persist, please check your network petitions with firebug.

(I can work open all my waves with two browsers).

One more comment. Websocket does not work under normal proxies. Are you under a proxy when you cannot open any wave?

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).

works well without proxy

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).

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.

nice to know!