Vicente J. Ruiz Jurado created WAVE-358:
-------------------------------------------
Summary: Some waves does not open randomly because of websockets
Key: WAVE-358
URL: https://issues.apache.org/jira/browse/WAVE-358
Project: Wave
Issue Type: Bug
Reporter: Vicente J. Ruiz Jurado
Hi there:
We are experiencing some problems with websocket.
Here a svg with websocket traces (click to move it):
http://homes.ourproject.org/~vjrj/otros/websocket-stuck.svg
And a text summary of the traces:
1-6 client auth and of open w+rxjxf59jf6i6A (correctly)
7 try to open w+1w2l4kbqi3p3l8 (->) without response so webclient stops waiting
in StagesTwo
8 opens again w+rxjxf59jf6i6A (->)
9-11 (<-) get the response for the w+1w2l4kbqi3p3l8 previously blocked (the
length is 13041, maybe this is the cause of the deadlock)
12-14 (<-) and immediately the response for w+rxjxf59jf6i6A that opens ok
This happens both with firefox and chromium and sometimes (for instance if you
reload the server or the client or wait for some time) the same problematic
wave opens correctly.
In firefox, if you disable websocket in about:config the same wave opens
correctly, so seems to me a jetty websocket issue.
Anyone experiencing similar problems?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
