Thanks, Roberto, I have periodic messages in the log saying this: - [uwsgi-websocket] no PONG received in 3 seconds !!!
The odd thing is that if happens, there are lots of these messages coming *at exact same time*, and many browser pages get disconnected. Again, at exact same time. The client code reconnects immediately, so that's not a big deal, but it feels something is wrong. do you have any idea why this might happen? P.S. After reducing the timeout to 10, these messages are much rarer, but still happen. As they are rare, it's hard to tell if they come at the same time, cause uwsgi does not log timestamps on non-request output. By the way, is there a way for uwsgi to to that? P.P.S. This error seems to happen right after "uwsgi.websocket_send()" was called in the code provided. The browser receives the message, but the next second there's websocket.onerror called. On Fri, Feb 28, 2014 at 1:13 AM, Roberto De Ioris <[email protected]> wrote: > > > Thanks for a fast answer Roberto, > > > > you probably missed the code in my second message, I did something very > > similar to the flask approach, > > > > oops, sorry you are right :) > > Btw, i would reduce the ping timeout, as there are few transaction in > place (and only from the server) i would send them every 10 seconds > (instead of 59) > > -- > Roberto De Ioris > http://unbit.it > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
