> Hi, Roberto, Jacob, > > actually considering the percent of these errors is very low (after > decreasing the timeout), and the fact that the browser reconnects > immediately, lowers the priority of this problem significantly. > > Though even if there's a long-blocking piece somewhere in the application > code, I don't know of it, and it seems it's extremely hard to track down. > > Jacob, the difference with your case is that this happens simultaneously > for several (but not all!) clients.
Hi, i think that the highest priority (now) is giving better infos in the error (at least the REMOTE_ADDR and the REQUEST_URI vars) I should be able to push a patch in the next few minutes > > > On Tue, Mar 11, 2014 at 3:20 PM, Jacob Rief <[email protected]> wrote: > >> 2014-02-28 19:18 GMT+01:00 Igor Katson <[email protected]>: >> >> 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. >>> >>> >> Hi Igor, >> I'am using uwsgi-2.0.2 and I also sometimes see: >> [uwsgi-websocket] no PONG received in 3 seconds !!! >> >> This happens, whenever the browser goes idle, for instance, when the >> screen saver of my laptop activates. >> Unfortunately, in Javascript this does not trigger a Websocket onerror >> event, otherwise it would be easy to have the browser reconnect to the >> server. >> >> - Jacob >> >> >> >> _______________________________________________ >> 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 > -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
